Page History

• Table occurrences: are always suffixed (not prefixed) with their "base table" name and separated using the » character ( Right-pointing Double Angle Quotation Mark – \x00BB ) using a space on either side of the ». The prefix is TitleCamelCase and indicates the functional area or use within the solution.
  ^{Option-Shift-Pipe (Mac) or Alt+0187 (Win)}

  Schedule » People	good
  A Persons Schedule	bad

  ^{This method of table occurrence naming is the inverse of the more popular method of using the "base table" name first. This requires a very strong focus to pre-define functional areas in your solution before hand! Sorting of table occurrence names is based on functional domain instead of base table name. Note, however, it's very easy to rename table occurrences if the functional realm changes for a particular group of table occurrences.}

Note: The goal of using FunctionalArea » Tablename is to force a degree of self documentation for the distinct areas of your solution. The FunctionalArea itself can be extended as long as it stays TitleCamelCase. For example:

NavigationAll » Menuitems
NavigationByAccess » Menuitems
NavigationPortal » Menuitems

Where Menuitems is a self explanatory table name and the keyword All may indicate a Cartesian product relationship, the keyword ByAccess indicates the involvement of a possible User table and the keyword Portal clearly indicates its use as a portal table occurrence.

NavigationAll__Menuitems
NavigationByAccess__Menuitems
NavigationPortal__Menuitems

^{@todo: should we come up with a list of suggested terms}

• Table occurrences: which are dedicated for internal development and have no relationships are prefixed with the @ symbol and one space
  ^{This sorts developer table occurrences at the top of the list for selecting tables}

  @ People	good
  Developer People Table	bad