projects / kivitendo-erp.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 30a5c52) | patch
generic_translations: DB-Upgrade in Perl geschrieben wg. Constraint-Namen
authorMoritz Bunkus <m.bunkus@linet-services.de>
Wed, 8 Jun 2016 14:05:09 +0000 (16:05 +0200)
committerMoritz Bunkus <m.bunkus@linet-services.de>
Wed, 8 Jun 2016 14:06:58 +0000 (16:06 +0200)
commit086e9880b6aeb6c3e95bcf4a4a84b985909346df
tree32fc3c69d94a0e3d1500d16f5e04fc9da2919848tree | snapshot
parent30a5c527c0feec009aed9e6915eb37fa1fdd9401commit | diff
generic_translations: DB-Upgrade in Perl geschrieben wg. Constraint-Namen

In alten PostgreSQL-Versionen hießen Foreign-Key-Constraints oft noch so
was wie »$1«. Da sich das Upgrade-Script also bzgl. des Namens nicht
sicher sein kann, gibt's momentan nur die Möglichkeit, einmal alle
Foreign-Keys zu einer Tabelle wegzuwerfen und diese neu anzulegen.

Dafür wiederum haben wir Support-Funktionen in SL::DBUpgrade2::Base, die
wie nutzen können. Also Umstellung des Scripts auf Perl.
sql/Pg-upgrade2/delete_from_generic_translations_on_language_deletion.pl [new file with mode: 0644] blob
sql/Pg-upgrade2/delete_from_generic_translations_on_language_deletion.sql [deleted file] blob | history
Unnamed repository; edit this file 'description' to name the repository.