#18297: Reverse generic relation to a model inheriting from the model defining a
generic relation confuses flush
-------------------------------+--------------------
     Reporter:  pronik         |      Owner:  nobody
         Type:  Bug            |     Status:  new
    Component:  Uncategorized  |    Version:  1.3
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 Please look into attached file, I've created a minimal test project for
 this bug. You'll have to include your database credentials in
 `settings.py` before you try it.

 Let's say we have model with a generic relation (e.g.
 `django.contrib.comments.models.Comment`) and a model deriving from it
 (e.g. `OtherComment`). Now, if a reverse generic relation to
 `OtherComment` is defined, it would correctly work and point to a list of
 `OtherComment` instances. However, `flush` would now try to reset the
 sequence on `id` field of `OtherComment` which does not exist
 (`OtherComment` only has `comment_ptr_id`) while resetting `id` on
 `Comment` would be correct.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18297>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to