Used database tables

For work with databases, two basic tables are used: projects table, where the descriptive information on projects is set, and point table, where the points are stored. Besides this other tables can be used (e.g. table containing the coordinate set names, contract types, scales, etc.).

Projects table

The projects table serves as the definition of projects (contracts). All the points are stored in one common table and contain the identifier of the project they belong to. Each point must belong to a specific project; the points not related to any project can't be saved in the database. Before storing the points, it is necessary to choose the project they belong to, or create a new project.

The minimum structure of the projects table is this:

  • Identifier

  • Project name

The identifier serves as a unique identification of the term in the database. Entering the identifier values must be done using the database means; GROMA doesn’t fill in this identifier when entering the record in the database (with the exception of the automatic database configuration, designed for work with graphic module). Therefore, it is necessary to configure the database so the identifier value fills in by itself. The best process is to assign to the identifier the feature AutoIncrement or to use triggers and sequences if allowed by the relevant database. In this case, the GROMA system must be informed that the identifier assignment is performed on the database level. This information is written in the definition file using the attribute value="auto" in the identifier column definition.

If the database is automatically configured for the needs of the graphic module from the GROMA system environment, then the identifier entry is taken care of by the GROMA system using internal sequences, so that it is not necessary to solve it on the database level.

The table structure can be extent by other not required user information; the GROMA system allows their editing, but won't use them for work. The usage of the user information is described in detail in the chapter Nastavení připojení k databázi.

The projects table can be edited directly from the GROMA system environment. After entering the command Database->Project settings a dialog window is displayed where you can perform project administration (adding, deleting, selecting).

Points table

The projects table serves for storing the points. All the points are stored in a common table, and their pertinence to a specific project is defined by the project identifier in the projects table. The points without pertinence to a project can't be stored in the database. Before storing the points, it is necessary to select the project to which the stored points are related or to create a new project.

The minimum structure of the points table is:

  • Identifier

  • Project identifier

  • Point number

  • Coordinate X

  • Coordinate Y

For the identifier, the same applies as for the Identifier in the points table.

Further, the table can contain the following optional data:

  • Coordinate Z

  • Quality code

  • Creation date

  • Last modification date

The table structure can be extended by other optional user information; the GROMA system will allow their editing but won’t use them for work. The detailed description of the usage of the user information is in the chapter Settings of the Nastavení připojení k databázi.

The projects table can be edited directly from the GROMA system environment. After entering the command Database->Project settings a dialog window is displayed where you can administer the projects (adding, deleting, selecting).