db-schema

Commit Graph

Author	SHA1	Message	Date
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
Victor Seva	1c77b0c04a	MT#10339 kamailio: upgrade to 4.3.0 This will be executed in every node in order to be able to have different versions during the upgrade process Change-Id: I0fd2b1c858f792b233b9fea348320c7635f4ebd2	11 years ago

Author

SHA1

Message

Date

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

Victor Seva

1c77b0c04a

MT#10339 kamailio: upgrade to 4.3.0

This will be executed in every node in order to
be able to have different versions during the upgrade
process

Change-Id: I0fd2b1c858f792b233b9fea348320c7635f4ebd2

2 Commits (27a4110cc6f0dddb3d02b7513534b2f8bcab8849)