English data model

Vertec’s interface has always been able to switch to English. But with this switch, only the terms on the user interface are translated. The underlying data model has always been in German, visible for example in the OCL editor and in the formulation of expressions such as projektbearbeiter.kuerzel.

As of Vertec 6.8, the Vertec data model is no longer only available in German, but also in English. This is intended to make it easier for non-German speaking customers to formulate OCL expressions or SQL queries, customize lists or write code.

Database in English

The database structure is created in English with Vertec 6.8, which means that the table and attribute names in the database can only be found in English.

In Vertec itself, this is not noticeable, because access is never directly to the database, but via the business logic. This means that OCL, SQL or XML queries work exactly the same as before, as the business logic knows all the classes, attributes and features in both German and English.

Existing databases are also converted to English when updating to Vertec 6.8. As the database is never accessed directly in Vertec, but always via the business logic, this change is not noticeable during operation.

Data model in English and German

In the case of the data model, both the existing German and the new English data model are valid in the same Vertec at the same time, so you can use the English and/or the German designations in the expressions.

For example, not only is an expression in the type projektbearbeiter->select(aktiv) valid, but also user->select(active). Mixed expressions also work: user->select(aktiv). This is the case throughout, also in function calls, via Python, in scripts, in lists, SQL folders etc.

However, each Vertec has a current model language: German for existing installations; English for new installations.

It has an impact on the display of members and the code completion in OCL editors, the display of class names (where they are not translated), and the following exceptions:

• When querying class names using string comparisons (e.g. ->select(class='Projekt')), the compared string must match the current model language. As it is not changed during an update, this does not affect backwards compatibility.
  • In order to formulate such queries in both German and English, an OCL operator containsType(Type)  has been introduced for type queries.  
• Projektbearbeiter is named User in English. However, the table in the database cannot be renamed USER because this is a reserved term. It is therefore called VTCUSER. SQL queries in English must be formulated accordingly.
  The SQL query is unchanged in German (also with English databases):

projektleiter IN (SELECT bold_id FROM projektbearbeiter WHERE kuerzel='\1')

In English, it must read as follows:

projectmanager IN (SELECT bold_id FROM vtcuser WHERE abbreviation='\1')