generated from it-at-m/oss-repository-en-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #486 from it-at-m/389-vereinheitlichung-db
doku update für db naming
- Loading branch information
Showing
2 changed files
with
27 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Uppercase-Convention für Datenbanken | ||
|
||
## Kontext | ||
|
||
Aktuell sind sowohl Namen als auch Properties der Datenbanktabellen mal in Uppercase, mal in Lowercase. | ||
Sofern Oracle und h2 nicht durch eine Änderung der migration-scripts auf Probleme stößt, wurde die Frage gestellt, die | ||
Tabellennamen und Properties zu vereinheitlichen. | ||
|
||
## Entscheidung | ||
|
||
Nachdem ein Renaming der migration-scripts gemäß Recherche möglich ist, werden die Skripte aller Services refactored: | ||
Syntax in Uppercase, Tabellenname, entsprechend der Klassenamen, in UpperCamelCase und die Properties in lowerCamelCase. | ||
|
||
Beispiel: | ||
|
||
```sql [V1_0__createWahlbezirk.sql] | ||
CREATE TABLE Wahlbezirk | ||
( | ||
id VARCHAR2(36) NOT NULL, | ||
wahlbezirkArt VARCHAR2(3) NOT NULL | ||
) |