OK thanks Karen, so the patch is the cause, foreign key filters now work fine with the 1.0.2 main release. Of course, once again I have the problem that tables with composite primary keys are not working...
I still don't understand why though. The class CompositePrimaryKey is not present in the main release. However, as neither my main table or the foreign key table had composite primary keys, why did the code use this class? Phil On Jun 24, 1:02 am, Karen Tracey <[email protected]> wrote: > On Tue, Jun 23, 2009 at 2:02 AM, Phil <[email protected]> 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 [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-users?hl=en -~----------~----~----~----~------~----~------~--~---
