MetaTable: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows: | The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows: | ||
;AUTHOR | |||
:(string) Database developer's name. | :(string) Database developer's name. | ||
;DATECREATED | |||
:(date) Defines the most recent date the database was edited or otherwise changed. | :(date) Defines the most recent date the database was edited or otherwise changed. | ||
;VERSION | |||
:(string) Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a [http://en.wikipedia.org/wiki/Globally_unique_identifier GUID]. After editing a timetable, this value should be changed. Values may be generated in a variety of ways; one useful way is to visit [http://createguid.com/ createguid.com]. | :(string) Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a [http://en.wikipedia.org/wiki/Globally_unique_identifier GUID]. After editing a timetable, this value should be changed. Values may be generated in a variety of ways; one useful way is to visit [http://createguid.com/ createguid.com]. | ||
;COMMENTS | |||
:(string) This field can be left empty. | :(string) This field can be left empty. | ||
Revision as of 01:10, 6 January 2011
The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows:
- AUTHOR
- (string) Database developer's name.
- DATECREATED
- (date) Defines the most recent date the database was edited or otherwise changed.
- VERSION
- (string) Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a GUID. After editing a timetable, this value should be changed. Values may be generated in a variety of ways; one useful way is to visit createguid.com.
- COMMENTS
- (string) This field can be left empty.