EULANDA® ERP System Head Start thru Technology
The naming convention of all SQL server objects, like tables, views, procedures, must follow regulate firm in order to guarantee an error free operational sequence of the EULANDA® business logic and in order to ensure the compatibility with future updates. This page contains a summary of these regulates.
TR [ < contraction creator> ]
| Operations | Abbreviation |
| INSERT | INS |
| UPDATE | UPD |
| DELETE | DEL |
| INSERT, UPDATE | INSUPD |
| INSERT, DELETE | INSDEL |
| UPDATE, DELETE | UPDDEL |
| INSERT, UPDATE, DELETE | ALL |
Afterwards can still more concisely understood follow, which describes the trigger.
Examples:
TR_USER_AF_UPD_StatusUeberwachung
TR_USER_AD_INSUPD_Historie
TR_DDHANDEL_RE_DEL_WaehrungsKurs
Procedure names begin with „cn_“. User procedures begin with „cn_user_“. Beside there are no further conventions. A good practice is to be used next the abbreviation of the table, which is concerned primarily (see also abbreviation listing (Abkürzungsverzeichnis)).
The names of the user tables may only with prefix "user" without the following underlined begin. Excluded are the contraction registered solution partner.
The names of the user view should begin with "USER_“.
Constraint names must with the standard contraction for the type followed of one underlined begin (see also name conventions).
"USER" must follow after the user constraints.