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
autogenerate doesn't render DEFERRABLE, INITIALLY, ONUPDATE, ONDELETE of ForeignKeyConstraint() #92
Comments
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Saif Hakim (@saifelse) wrote: I don't see support for initially in create_foreign_key. Am I missing something? |
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Tim Mitchell wrote: I had this issue crop up again in alembic-0.7.5.post2. |
Michael Bayer (@zzzeek) wrote: @tim_mitchell - can you please provide more detail? Was this issue resolved for you and then stopped working? Can you provide specifics about the move of an FK here? the create for the FK is using the FK with the arguments you've given it and the above changeset has tests for this (see https://bitbucket.org/zzzeek/alembic/commits/0ed20805f3f32de768b9b4eb9eebc9c3e0ac7453#Ltests/test_autogenerate.pyT957) |
Tim Mitchell wrote: I have only been using alembic for about a month. All added constraints show this defect. None of your tests appear to test multiple keyword arguments as is always the case in my situation. Here is excerpts from my code which is hopefully enough to reproduce.
|
Tim Mitchell wrote: Have just noticed that compare_metadata() does not notice the differing ondelete clauses either. |
Migrated issue, originally created by Michael Bayer (@zzzeek)
The text was updated successfully, but these errors were encountered: