Geek asks and answers

Span integration in the production database

We have a database in production that already has a large number of rows in the user table. Review the following instructions on the flyway website:

If you have an existing database that was not populated by Flyway this is the way to go:

  • Create an initial migration script that recreates your current one and give it a low version number.
  • Use flyway: init to create a metadata table and set this script as the current version.

I would like to use flyway to manage my schema and various constants in the database, but I do not want V1__Base_version.sql to contain account information for our current users, especially considering that it is stored in SCM. If I understand these instructions correctly, I will need the ability to "recreate [my] current state" using V1__Base_version.sql.

So, will the initial migration only be using the circuit, and the constants work fine? Or should the databases on our workstations correspond to those that are 100% produced?

+5
source share
1 answer

You're right. The init command is for marking a production database with a version.

, ( PROD db), . PROD, init. , , .

+7

More articles:


All Articles