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

Bump migrations to v2.x #1464

Closed
Jeckerson opened this issue Jun 9, 2020 · 1 comment
Closed

Bump migrations to v2.x #1464

Jeckerson opened this issue Jun 9, 2020 · 1 comment

Comments

@Jeckerson
Copy link
Member

Jeckerson commented Jun 9, 2020

Update from v1 to v2 and check if all works.
Also check if migrations from v1 are compatible with v2. If so, release it with devtools v4.1 instead of v5.0

@BeMySlaveDarlin
Copy link
Contributor

Migrations v1 and v2 compatibility tests

  • Mysql (tested: percona, mariadb, mysql 5.6 | skipped: mysql 8, mysql clustered, mysql master-slave scheme)
    • generate/run
    • all column types
    • morph, up, down
    • datasets
    • command options
  • Postrgesql (tested: 9.6, 10-12 | skipped pg cluster)
    • generate/run
    • all column types
    • morph, up, down
    • datasets
    • command options

Common minor issues:

  • Command calls different - v1 requires extra argument in call phalcon-migrations migration [command] [options]
  • Minor differs in exception outputs
  • Minor differs in cases of code parts
  • v2 and devtools 4.0.x cannot be installed together

@Jeckerson Jeckerson added this to Working on it in Phalcon Roadmap Mar 31, 2021
Phalcon Roadmap automation moved this from Working on it to Implemented Apr 9, 2021
Phalcon ecosystem board automation moved this from In Progress to Done Apr 9, 2021
@niden niden moved this from Implemented to Released in Phalcon Roadmap Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants