RidgeStar
About
Locations
Manual
Preface
Introduction
Versions
Concepts
Construction
Usage
Operations
Questions
Features
Settings
Internals
Cookies
Database
Debug
Diagnose
Properties
Server Software
Setsql
Appendices
Reference
Service
Logon
RidgeStar

Manual: Internals-Database

Logontranslate
Get Started |Calendar |Locations

Each RidgeStar Interactive SiteInteractive Site is driven by the contents of a MariaDB-> Database, which consists of multiple Tables. Each Table contains one or more data Fields that hold a bit of information about the object of the table.

Typical Tables

MariaDBA Referee Management Site can contain anywhere from 4 to 40 Database Tables, depending on the interactivity of the Site's operations. A typical combination of Tables include the following:

  • Users: Contains an entry for each UserUser authorized to access the Site
  • Matches: Contains an entry for each scheduled competition
  • Accounting: Contains an entry for each fiscal transaction between the Chapter and a Referee
  • Fields: Contains an entry for each space at a Location that can host a Match
  • Locations: Contains an entry for each single street address containing one or more Fields
  • Options: Contains an entry for each operational aspect of the Site
  • Topics: Contains an entry for each Topic and Subtopic available from the HELP or FAQ tools
  • Text: Contains individual elements associated with a Topic

Field Naming Standards

Every unique Database Field is named using the following format:

dxxName

Where:

d
the letter "d" means "database" and identifies the data element as residing from or being destined for the database
xx
two letters/numbers that identify the table. For example, "us" typically identifies the element as being associated with the "Users" table.
Name
letters/numbers that identify the purpose of the data elements (e.g. dusFirstName, dusBirthDate, dusAddress are data elements from the Users database table)

In general, the 4th character of the element name is in UPPER case with the 5th and subsequent characters either UPPER or lower case, which ever represents the contents of the field most appropriately.