-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Proxy models ignore lessons of their base models #157
Comments
Nice catch! Would you have time to create a PR for this? |
PoByBolek
added a commit
to PoByBolek/django-dynamic-fixture
that referenced
this issue
Sep 15, 2023
Seems like I do: #161 |
paulocheque
pushed a commit
that referenced
this issue
Sep 15, 2023
Awesome! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the Django docs it sounds like proxy models and regular models are basically equivalent when it comes to database access. The proxy models just add extra methods or managers that the regular models don't have.
Based on this I was also expecting that DDF reuses the lessons for concrete models for any proxy models they might have. But this doesn't seem to be the case 😞
G()
etting a proxy model works just fine, but DDF ignores any lessons that I have taught for the concrete base model.When I run the tests using
python manage.py test
, the test fails:I currently work aroung this by specifically copying the lessons for proxy models from their concrete base models. But it would be nicer if DDF supported this out of the box 😸. Maybe if
DDFLibrary.get_configuration()
andDDFLibrary.add_configuration()
checked for proxy models themselves?The text was updated successfully, but these errors were encountered: