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
Unique index naming conflict with atlas #2421
Comments
Still present on master as of today. I updated the demo repo. |
a8m
added a commit
that referenced
this issue
Mar 28, 2022
a8m
added a commit
that referenced
this issue
Mar 28, 2022
Thanks for reporting this @pzeinlinger 🙏 Fixed with #2433 |
gitlawr
pushed a commit
to gitlawr/ent
that referenced
this issue
Apr 13, 2022
gitlawr
pushed a commit
to seal-io/ent
that referenced
this issue
Apr 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior 😯
Using atlas as migration engine leads to a naming conflict of columns with unique constraints using sqlite. Migrations with Postgres work as expected.
Output of debug client:
db: sqlite
Expected Behavior 🤔
Ent's old migration engine used sqlite's auto index
Steps to Reproduce 🕹
Minimal Reproducible Example
Your Environment 🌎
The text was updated successfully, but these errors were encountered: