Just a heads up, I've made changes to Sequel's master branch so that when PostgreSQL 10.2+ is used, primary_key will create identity columns instead of serial columns. Identity columns work very similarly to serial columns, but have a number of advantages. See https://blog.2ndquadrant.com/postgresql-10-identity-columns/ for details.
This change could possible be backwards compatible in some minor way. I think the benefits are worth the potential backwards compatibility issues, so in the master branch identity columns are automatically used on 10.2+, with no option to use serial columns. However, I'd like to get feedback from the community regarding this change. If you feel strongly that Sequel should provide the option to use serial columns by default, or that Sequel should continue to use serial columns by default and make use of identity columns opt-in, then please post here with your reasoning and the specific problems you see with switching to identity columns. I'm willing to consider using serial instead of identity by default until the release of Sequel 5.7.0. If Sequel 5.7.0 ships with identity columns by default, that will remain the future behavior, though I'll be willing to consider supporting serial as an option afterward. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
