MetaTable: Difference between revisions

From SignalWiki
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:


:Field: AUTHOR
:AUTHOR
:Type: string  
:(string) Database developer's name.
:Purpose: Database developer's name.


Field: DATECREATED   
:DATECREATED   
Type: date  
:(date) Defines the most recent date the database was edited or otherwise changed.
Purpose: Defines the most recent date the database was edited or otherwise changed.


Field: VERSION
:VERSION
Type: string
:(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].
Purpose: 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].


Field: COMMENTS
:COMMENTS
Type: string
:(string) This field can be left empty.
Purpose: This field can be left empty.

Revision as of 00:53, 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.
COMMENTS
(string) This field can be left empty.