On Tue, Jun 23, 2009 at 2:02 AM, Phil <but...@gmail.com> wrote: > I'm sure I had this working before, but since then I have installed > the composite primary key patch and I notice the 2nd to last traceback > is in class CompositePrimaryKey... Could this be something to do with > it?? All ideas appreciated >
Certainly if you see code from the patch in the traceback then I'd be inclined to suspect the patch as the cause. Next step would be to try to recreate the error without the patch -- if you can't, that would be more evidence there is some situation the patch isn't handling properly. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
