Gold Warehouse Database adaptation
Operating instructions:
Add schema= "Public" to all entity layers of the program(public here is a schema defined by the database)
Second, switch the database, modify the configuration file Cms.properties inside the cms.dbtype=kingbase(fill in the database need to change)
:
Note: Fill in the corresponding types of databases: NTU General database > GBASEDBT Warehouse database "kingbase
Dream Database " db
Iii. use of Kanakura Database Tools
after migrating the data from other databases and the table structure to the Warehouse database management tool through the Warehouse Database Migration Tool, manually add the table with the identity for all of its table structures .
:
:
Iv. configuration file format
Precautions:
(1), Kanakura database, dream Database No need to modify the database dialect
(2), the adaptation of the Dream database and the suitability of the warehouse database are consistent.
(3),
South Big Universal Database adaptation
I. Modification of the database dialect
modified to hibernate.dialect= in the \publms\src\main\resources\config\hibernate.properties configuration Com
:
Note: The dialect here is my own modification of the definition. So the path is in the program.
The schema= "public" defined by the entity layer in all Programs is not required (removed). :
III. management tools for the general database of the south
(1), the South Large General database Migration Tool, the migration needs to modify the corresponding modifier. :
(2), through the Migration tool of the NTU universal database and the data of other databases migrated and the table structure into the Warehouse database management tool, the table with the self-increment of all its table structure using SERIAL8 this to manually add.
:
Iv. primary key policy in the program
Modify the primary key policy to:Org.hibernate.id.IncrementGenerator
Five, the final configuration file format
Domestic database adaptable to