Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transparently upgrade metadata table from 3.x to 4.x format #1117

Closed
7 tasks done
axelfontaine opened this issue Oct 28, 2015 · 8 comments
Closed
7 tasks done

Transparently upgrade metadata table from 3.x to 4.x format #1117

axelfontaine opened this issue Oct 28, 2015 · 8 comments

Comments

@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Oct 28, 2015

  • MigrationType INIT -> BASELINE
  • Recalculate checksums by ignoring line endings
  • Drop version_rank column
  • Make version nullable
  • Make installed_rank the new primary key
  • Drop installed_rank index
  • Drop version_rank index
@axelfontaine axelfontaine added this to the Flyway 4.0 milestone Oct 28, 2015
@axelfontaine axelfontaine changed the title Transparantly upgrade metadata table from 3.x to 4.x format Transparently upgrade metadata table from 3.x to 4.x format Oct 28, 2015
@numero-six
Copy link

@numero-six numero-six commented Jan 29, 2016

Recalculate checksums by ignoring line endings

In my opinion, we should also ignore comments. Many copyright and licensing policies require to place a license header on every file of a project. It means that if the project using Flyway has its license changed, all checksum will changes, raising Flyway errors.

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 15, 2016

@cteig Flyway 4.0 will be released next week. Can you check this week that MigrationTestCase.upgradeMetadataTableTo40Format() passes for DB2 zOS to ensure those users will have a smooth migration path to Flyway 4.0? Thanks! Axel

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 15, 2016

@nathanvick Flyway 4.0 will be released next week. Can you check this week that MigrationTestCase.upgradeMetadataTableTo40Format() passes for Redshift & Vertica to ensure those users will have a smooth migration path to Flyway 4.0? Thanks! Axel

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 15, 2016

@MichaelF25 Flyway 4.0 will be released next week. Can you check this week that MigrationTestCase.upgradeMetadataTableTo40Format() passes for SolidDB to ensure those users will have a smooth migration path to Flyway 4.0? Thanks! Axel

@nathanvick
Copy link
Contributor

@nathanvick nathanvick commented Feb 22, 2016

@axelfontaine,

I regret that I've been feeling sick this week. I hope get to it early this
week.

-Nathan

On Mon, Feb 15, 2016, 4:37 AM Axel Fontaine notifications@github.com
wrote:

@nathanvick https://github.com/nathanvick Flyway 4.0 will be released
next week. Can you check this week that
MigrationTestCase.upgradeMetadataTableTo40Format() passes for Redshift &
Vertica to ensure those users will have a smooth migration path to Flyway
4.0.


Reply to this email directly or view it on GitHub
#1117 (comment).

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 22, 2016

@MichaelF25 Did you have a chance to check this?

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 22, 2016

@nathanvick No worries. Worst case this will be for 4.0.1

@MichaelF25
Copy link
Contributor

@MichaelF25 MichaelF25 commented Feb 23, 2016

@axelfontaine I am now working for a different company and we do not use SolidDB. I've handed over this issue to my former colleagues and hopefully one of them will provide an update about this issue soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants