On Wed, Jan 30, 2013 at 4:30 PM, Dylan Klomparens <[email protected]> wrote: > Hello, > > I've encountered what may be a Django ORM bug and am writing to see what the > dev community thinks. I have a model that uses generic relations. An error > is returned when I attempt to delete multiple rows of said model in the > database table. The error is repeatable, and I have found it is only > applicable to models that contain generic relations. The error occurs after > the deletion is confirmed in the admin interface and the SQL statement > begins execution. > > I've attached the use case that creates the bug, the generated SQL statement > (read from the debug output), and the model in question. > > Could someone please confirm that this is indeed a bug? If so, I can create > a ticket and begin researching how to remedy this problem.
I can confirm that the attached SQL is problematic for Oracle. It has an ORDER BY clause inside an IN subquery, which is meaningless in general and not permitted by Oracle. However, I was not able to confirm the bug using Django 1.5rc1 and Oracle 10g XE. I tried replicating the case with the model provided, and the multiple deletion was successful. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
