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

--force=true does not overwrite migration and db table #28

Closed
ja-tomasz opened this issue Feb 3, 2017 · 1 comment
Closed

--force=true does not overwrite migration and db table #28

ja-tomasz opened this issue Feb 3, 2017 · 1 comment
Labels
duplicate

Comments

@ja-tomasz
Copy link

If I realize I made a mistake in the model definition and I run resource(s) generator again (--force=true), it creates another migration, with new timestamp and either fails when trying to declare again the migration class with the same name or fails when running the migration, because the table already exists in the db.

Probably this also applies to the model and migration generator.
@webNeat
Copy link
Owner

webNeat commented Feb 3, 2017

I guess this is duplicate of the previous issue.
Please refer to it :)

@webNeat webNeat closed this as completed Feb 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@webNeat @ja-tomasz