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

Migrations: Fresh install / first run is different to an upgrade #732

Closed
ErisDS opened this issue Sep 14, 2013 · 0 comments
Closed

Migrations: Fresh install / first run is different to an upgrade #732

ErisDS opened this issue Sep 14, 2013 · 0 comments
Assignees
@ErisDS
Milestone
0.3

Comments

@ErisDS
Copy link
Member

ErisDS commented Sep 14, 2013

From #482:

Migrations should deal with a fresh install differently to an upgrade, including managing fixtures and settings being loaded: #731

They should also throw sensible error messages if the currentVersion is too high or not readable.

currentVersion should be kept track of by the migration controller,

currentVersion should probably be renamed to databaseVersion
@ghost ghost assigned ErisDS Sep 14, 2013
@ErisDS ErisDS mentioned this issue Sep 14, 2013
Closed
@ErisDS ErisDS closed this as completed in 0243664 Sep 14, 2013
This was referenced Jul 10, 2020
Open
Open
This was referenced Aug 17, 2020
Open
Open
@snyk-bot snyk-bot mentioned this issue Aug 28, 2020
Open
@skmezanul skmezanul mentioned this issue Feb 23, 2021
Open
@skmezanul skmezanul mentioned this issue Sep 30, 2022
Open
@mdno mdno mentioned this issue Feb 28, 2024
Open
@amgir amgir mentioned this issue Feb 29, 2024
Open
@MartialSeron MartialSeron mentioned this issue Apr 15, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ErisDS ErisDS

Labels
None yet
Projects
None yet
Milestone
0.3
Development

No branches or pull requests
1 participant
@ErisDS