Rohit Yadav c63dbb8804 db: Refactor new change in create-schema/premium to schema40-410.sql ...

- Move changes since 4.0 to schema upgrade path (schema40-410.sql)
- Comment out some table names where we're trying to copy uuid from id, they
  don't exists
- We don't run above step for tables which are newly created for 410 and don't
  exist in 4.0 for example autoscale related ones, code is commented and not removed
- Drop indexes which are removed before dropping the column
- Comment out insertion, as for default region we're inserting the same in
  code, in ConfigurationServerImpl:createDefaultRegion(), fix same in premium

Testing;
Deployed fresh 4.0 database, compiled and ran mgmt server. It did a smooth
rolling upgrade from 4.0 to 4.1.0 with no database exceptions or any other db error.

TODO:
- 4.2.0 relates changes like ipv6 should go into its schema-410to420.sql

Signed-off-by: Rohit Yadav <bhaisaab@apache.org>

2013-02-16 17:12:26 +05:30

..

bindir

db: Remove and merge 4.1-new-db-schema.sql to schema-40to410.sql

2013-02-16 12:44:45 +05:30

db

db: Refactor new change in create-schema/premium to schema40-410.sql

2013-02-16 17:12:26 +05:30