Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support identity columns #730

Closed
CaselIT opened this issue Aug 21, 2020 · 1 comment
Closed

Support identity columns #730

CaselIT opened this issue Aug 21, 2020 · 1 comment
Labels
autogenerate - defaults autogenerate - detection autogenerate - rendering feature

Comments

@CaselIT
Copy link
Member

CaselIT commented Aug 21, 2020

This is just a placeholder
After sqlalchemy/sqlalchemy#5527 is done support for identity columns should be added to alembic
@jvanasco jvanasco mentioned this issue Aug 24, 2020
Closed
@sqla-tester
Copy link
Collaborator

CaselIT has proposed a fix for this issue in the master branch:

Add support identity columns. https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/2371

liZe added a commit to endlessm/azafea that referenced this issue Mar 25, 2021
@liZe
Set IDENTITY as default server versions for migration events
d3577e6 
Thanks to SQLAlchemy 1.4, Alembic now knows how to handle identities (see
sqlalchemy/alembic#730).

For unknown reasons, identities are now detected as server default values for
the Event table, and are put in database migrations. Explicitely setting the
default value fixes the new alembic migrations, at least for tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
autogenerate - defaults autogenerate - detection autogenerate - rendering feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sqla-tester @CaselIT