#26413: Abstract model inheritance regression with string model references in
1.9
-------------------------------------+-------------------------------------
Reporter: trkjgrdg | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* cc: AlexHill, charettes (added)
* stage: Unreviewed => Accepted
* component: Uncategorized => Database layer (models, ORM)
* severity: Normal => Release blocker
Comment:
This worked in 1.8.
Bisected the change in behavior to
9239f1dda7b94f53d21efb8b5e4d056e24f4e906 (Refs #24215 -- Prevented pending
lookup pollution by abstract models.) by charettes. The error is
`OperationalError: no such column: t26413_c.a_ptr_id` at that point.
The error changes to `AttributeError: 'str' object has no attribute
'_meta'` at 720ff740e70e649a97fcf0232fec132569a52c7e (Fixed #24215 --
Refactored lazy model operations) by Alex Hill.
--
Ticket URL: <https://code.djangoproject.com/ticket/26413#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.860e297bd25da517746e9118bb12e9dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
