-
Notifications
You must be signed in to change notification settings - Fork 312
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
[Postgres] schema command fails: error: sql: Scan error on column index 1, name "enumsortorder" #344
Comments
Hey, thanks for submitting an issue! It's really hard to help debug the problem when we dont have access to the schema :(. If you share more information including a way to reproduce the error, it makes it easier for us to help |
I understand. I was hoping to first see if the error made it clear what in the schema would be causing this. I unfortunately cannot share the schema entirely. We're debugging this and will report back with more info. It seems there's a problem with an enum using a non-int value and an index with a conversion. |
I can confirm that's the source of this problem - an enum with a non-int value (in this case, it is The other error, which I can open a separate issue for if you'd like, is |
I created a new issue for the second problem: #345 |
This was the result of a migration that added a value before another. IE:
|
Trying to generate a schema with
xo
for the first time.The text was updated successfully, but these errors were encountered: