This page has been archived
- Please Do Not Edit
Pages placed in this namespace. The pages in the Archived
namespace exist only as a historical reference, it will not be improved and its content may be incomplete.
General Naming Conventions
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
Field Type Recommendations