We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the database I'm working with, this part is unstable because it doesn't define ORDER BY:
ORDER BY
ARRAY(SELECT enumlabel FROM pg_catalog.pg_enum WHERE enumtypid = t.oid)
alembic-postgresql-enum/alembic_postgresql_enum/get_enum_data.py
Lines 66 to 77 in fa7626e
SELECT enumlabel FROM pg_catalog.pg_enum WHERE enumtypid = 8175864; enumlabel ---------------------------- comment findings history impression_recommendations technique
If I include the enumsortorder, it gives a different result:
enumsortorder
SELECT enumlabel, enumsortorder FROM pg_catalog.pg_enum WHERE enumtypid = 8175864 ORDER BY enumsortorder; enumlabel | enumsortorder ----------------------------+--------------- history | 1 technique | 2 findings | 3 comment | 4 impression_recommendations | 5
Performing VACUUM FULL does fix this. I assume that's because it reorganises the underlying postgres structures (ctid)?
VACUUM FULL
ctid
The text was updated successfully, but these errors were encountered:
Order defined enums by enumsortorder. Fixes Pogchamp-company#31
23c652a
Successfully merging a pull request may close this issue.
In the database I'm working with, this part is unstable because it doesn't define
ORDER BY
:alembic-postgresql-enum/alembic_postgresql_enum/get_enum_data.py
Lines 66 to 77 in fa7626e
Examples
If I include the
enumsortorder
, it gives a different result:Performing
VACUUM FULL
does fix this. I assume that's because it reorganises the underlying postgres structures (ctid
)?The text was updated successfully, but these errors were encountered: