Hanne, I ran into that exact problem myself and filed the following ticket related to the issue: http://code.djangoproject.com/ticket/9519
I also found that you could run your own delete operation through the ORM, however, to work around this. It's more work and certainly not in line with DRY or any of the normal sensibilities... but it does at least work. Here's an example of that, built off the example in the ticket: http://dpaste.com/92116/ On Wed, Nov 19, 2008 at 05:07, Hanne Moa <[EMAIL PROTECTED]> wrote: > > Funny thing though, got a manytomany-table without a primary key: I > can add a new row easily enough, the only problem is in delete()-ing > specific rows, since that seems to use the primary key. So I clear() > and re-add instead of delete()-ing, since that doesn't use the primary > key. Fragile, but it beats doing the puppy-eyes to the DBA. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
