#11437: [soc2009/multidb] M2M Relationship with through=[model] whose primary key
is renamed fails with wrong column name
---------------------------------------------------+------------------------
Reporter: anonymous | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: soc2009/multidb
Resolution: | Keywords: multidb manytomany db_column
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by anonymous):
I'll try to reproduce it with the models you added (in the diff), but I
can't try it out right now. A quick glance shows that you don't have the
using='otherdb' in all of the meta classes, but I'm not sure if that's the
reason I'm encountering this.
Further info: This occurs when the admin tries to get a list of objects to
delete. That is, I go to edit a particular instance of the model (in your
example, it'd be the Author model) to view the admin's object_detail page,
and then click delete there, I get the OperationalError. The query happens
when getting a list of objects to delete, but does not happen if the
object i selected has no entries in the M2M bridge table.
Again, i'll check it out in a bit.
PS: Great work on the new multidb branch, almost all of it is working
seamlessly.
--
Ticket URL: <
http://code.djangoproject.com/ticket/11437#comment:2>
Django <
http://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
django-updates@...
To unsubscribe from this group, send email to
django-updates+unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en-~----------~----~----~----~------~----~------~--~---
