Difference between revisions of "Database schema standards"
From Joomla! Documentation
| Line 8: | Line 8: | ||
* Pascal casing. This practice is known by many other names, but will be referred to here as Pascal casing. This involves using a capital letter at the beginning of each new word. | * Pascal casing. This practice is known by many other names, but will be referred to here as Pascal casing. This involves using a capital letter at the beginning of each new word. | ||
Examples: ExampleTable, TableOfContents | Examples: ExampleTable, TableOfContents | ||
| + | |||
| + | * Singular names. The use of singular names is just a simpler way of writing names. While plural names could be used, singular names are shorter and easier to understand. | ||
| + | Example: Student (as opposed the Students) | ||
| + | |||
| + | * Simple, yet describes the contents of the table or field. Names should be as small as possible, while still giving a user a clear indication of its contents. | ||
| + | |||
| + | * Avoid similar names. When making larger databases, and having many tables, the tables should be clearly identifiable. If 2 or more tables have similar names, consider renaming one of the tables or combining the contents of them both. The same could be said for fields, to a lesser extent. | ||
| + | |||
Revision as of 20:19, 30 September 2012
This page has been archived. This page contains information for an unsupported Joomla! version or is no longer relevant. It exists only as a historical reference, it will not be improved and its content may be incomplete and/or contain broken links.
Naming Conventions[edit]
General Naming Conventions[edit]
There are many conventions used when naming tables or fields, so others are capable of understanding the contents of the table. While there are no absolute conventions, the following are used quite often, with the intention of clearer SQL statements.
- No spaces. Using spaces is highly not advised when naming tables or fields. It makes SQL statements more complicated and harder to understand. In order to identify a gap in between words, underscores could be used. However, the preferred method is the use of Pascal casing.
- Pascal casing. This practice is known by many other names, but will be referred to here as Pascal casing. This involves using a capital letter at the beginning of each new word.
Examples: ExampleTable, TableOfContents
- Singular names. The use of singular names is just a simpler way of writing names. While plural names could be used, singular names are shorter and easier to understand.
Example: Student (as opposed the Students)
- Simple, yet describes the contents of the table or field. Names should be as small as possible, while still giving a user a clear indication of its contents.
- Avoid similar names. When making larger databases, and having many tables, the tables should be clearly identifiable. If 2 or more tables have similar names, consider renaming one of the tables or combining the contents of them both. The same could be said for fields, to a lesser extent.
Field Naming Conventions[edit]
Field Type Recommendations[edit]
This archived page is actively undergoing a major edit for a short while.
As a courtesy, please do not edit this page while this message is displayed. The user who added this notice will be listed in the page history. This message is intended to help reduce edit conflicts; please remove it between editing sessions to allow others to edit the page.
If this page has not been edited for several hours, please remove this template, or replace it with {{underconstruction}} or {{incomplete}}.