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

Dirty Database Troubleshooting Docs #337

Closed
bpmooch opened this issue Feb 13, 2020 · 3 comments
Closed

Dirty Database Troubleshooting Docs #337

bpmooch opened this issue Feb 13, 2020 · 3 comments

Comments

@bpmooch
Copy link

bpmooch commented Feb 13, 2020

Is your feature request related to a problem? Please describe.
In working through learning how to use this migration tool, I ran into an issue where I wrote some silly SQL with a syntax error, resulting in me getting this error upon rerunning the migrations after fixing the SQL syntax issues - error: Dirty database version 0. Fix and force version. Maybe I have not exhaustively searched the docs for the answer on how to troubleshoot this, but looking around made me think some troubleshooting steps for this issue should be present in the FAQ. For me specifically, I am unsure how to "force a version"

Describe the solution you'd like
I think the docs should be updated to include some more explicit troubleshooting for this issue. I'm suggesting an addition to the FAQ near the explanation of what a dirty database means.

Describe alternatives you've considered
If this already exists in the docs, please point me there. I still think, however, that this information could be better surfaced to folks browsing the repo if it is already available.

@dhui
Copy link
Member

dhui commented Feb 15, 2020

Yeah, the docs aren't very well organized. Any help you can offer to clean up the docs would be greatly appreciated!

Some options include updating GETTING_STARTED and/or FAQ to mention the migrate force CLI and migrate.Migrate.Force()

See also: #40

@mknycha
Copy link
Contributor

mknycha commented Feb 26, 2020

I remember I also needed to check out closed issues on github to figure out how migrate force works. It is pretty well described in #282, hope this will help you

@dhui
Copy link
Member

dhui commented Mar 26, 2020

Fixed in #361
Thanks @mknycha for helping others with this issue and for the PR!

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

No branches or pull requests

3 participants