-
-
Notifications
You must be signed in to change notification settings - Fork 901
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
Broken compatibility on generation of joined table inheritance with abstract models #470
Comments
Yes, that should work, this is a bug. Probably related to popping the tablename attribute without checking if it's a declared attr. |
The sole existence of the |
It's related to test case
I suggest adding a test case as well. |
This test from #541 should cover this case. If a declared attr name is found, a new name is not set. Note that using |
First of all many thanks for releasing 2.2!
Here is the test case for my problem:
It's a bit long but please bear with me; all equality assertions pass greatly but calling
db.create_all()
raises following exception:Interestingly we have:
bad_employee
andbad_engineer
, notbademployee
andbadengineer
. It was working in 2.1, stopped in 2.2 (probably after #467). Do you plan to support such test case?The text was updated successfully, but these errors were encountered: