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.

Sign up for GitHub

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

Jump to bottom

[NFR] Generate new migration only on changed structure #16

Open
ruudboon opened this issue Nov 28, 2019 · 0 comments
Open

[NFR] Generate new migration only on changed structure #16

ruudboon opened this issue Nov 28, 2019 · 0 comments
Assignees
@Jeckerson
Labels
NFR New Feature Request

Comments

@ruudboon
Copy link
Member

It would be nice if there is an option to skip the generation when de database structure isn't changed.
For example when there is a migration (v1.0.0) and nothing has changed running the generate will result in something like:

vendor/bin/phalcon-migrations migration generate
Database hasn't changed. Skipped generation. Run migration generate --force to force generating a new version.
@ruudboon ruudboon added the NFR New Feature Request label Nov 28, 2019
@Jeckerson Jeckerson added this to the 1.2.x milestone Jan 28, 2020
@Jeckerson Jeckerson self-assigned this Jan 28, 2020
@Jeckerson Jeckerson modified the milestones: 1.2.x, 1.1.x Jan 28, 2020
@Jeckerson Jeckerson modified the milestones: 1.2.x, 2.0.x Feb 23, 2020
@Jeckerson Jeckerson modified the milestones: 2.0.x, 2.1.x, 3.0.x Mar 19, 2020
@niden niden added this to Phalcon v5 Aug 25, 2022
@niden niden moved this to Backlog in Phalcon v5 Aug 25, 2022
@Jeckerson Jeckerson removed this from the 3.0.x milestone May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jeckerson Jeckerson

Labels
NFR New Feature Request
Projects
Phalcon v5
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Jeckerson @ruudboon