db-schema

Commit Graph

Author	SHA1	Message	Date
Kirill Solomko	2234f05ddf	TT#47713 fix table locks in 15251_not_replicated.up * addresses an issue with the foreign key cannot be recreated as it relies on the lnp_providers table, affected since MariaDB 10.1.37 Change-Id: I785fcae727e975839c710f327bd10a659384c39c	7 years ago
Kirill Solomko	8e03d7b475	MT#22031 cosmetic up script changes for MariaDB compatibility * "partition" is a reserved word in MariaDB and as such the existing column with name partition is escaped as `partition` * MariaDB is more restrictive to column alterations that have foreign keys in another tables and as such added constract drop/add wrapped into LOCK TABLES. LOCK TABLES is essential there as after DROP FOREIGN KEY up until the CONSTRANT is recreated again there is a chance to break the consistency with a wrong sql statement executed when the up script is being applied. Change-Id: I4b08a1c5b2c5e1632e2683f62251fe3873ebc58e	9 years ago
Rene Krenn	bd3911b9ac	MT#20023 MT#20027 lnp numbers unique contraint and restrict delete cascade +replace old lnp_provider_id index by multi-column unique index (safe one index) +not replicated, as lnp_numbers table could get large Change-Id: I776358e42345f9a58bd3c755f7e40b12c1ac0a25	9 years ago

Author

SHA1

Message

Date

Kirill Solomko

2234f05ddf

TT#47713 fix table locks in 15251_not_replicated.up

* addresses an issue with the foreign key cannot be
      recreated as it relies on the lnp_providers table,
      affected since MariaDB 10.1.37

Change-Id: I785fcae727e975839c710f327bd10a659384c39c

Kirill Solomko

8e03d7b475

MT#22031 cosmetic up script changes for MariaDB compatibility

* "partition" is a reserved word in MariaDB and as such
      the existing column with name partition is escaped
      as `partition`
    * MariaDB is more restrictive to column alterations that have
      foreign keys in another tables and as such added
      constract drop/add wrapped into LOCK TABLES.
      LOCK TABLES is essential there as after DROP FOREIGN KEY
      up until the CONSTRANT is recreated again there is a chance
      to break the consistency with a wrong sql statement executed
      when the up script is being applied.

Change-Id: I4b08a1c5b2c5e1632e2683f62251fe3873ebc58e

Rene Krenn

bd3911b9ac

MT#20023 MT#20027 lnp numbers unique contraint and restrict delete cascade

+replace old lnp_provider_id index by multi-column unique index
 (safe one index)
+not replicated, as lnp_numbers table could get large

Change-Id: I776358e42345f9a58bd3c755f7e40b12c1ac0a25

3 Commits (ad7618703562f5f925d30f1fff0be2da80d6db46)