Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From Postgres 10 onwards,
IDENTITY
columns seem to be favored (at least by Sequel) overserial
columns. After updating Sequel, I now get an error for thebigserial
columns, because it tries to make it anidentity
column with typebigserial
. I believe this is a bug in Sequel, but I haven't been able to make a self-contained example for this.The easiest solution would be to use
bigint
columns, but I'm not sure about the impact on the Hets/Haskell side here, especially when Postgres < 10 is used. @eugenk maybe you know if this is a critical change or if looking for another solution would be better.This is the generated SQL query:
and the error:
What's strange is that this code works:it only worked because I accidently used a different Ruby version with a different Gem version.as it generates this query: