On Wed, 2007-03-14 at 21:16 +0100, Roland Hedberg wrote: > Hi Rubic, > > Rubic wrote: > > Roland, > > > > The error message isn't the most helpful. ;-) > > I'll second that ! > > > I had a similar problem back in January and tracked it > > down to ticket #2536. My workaround was changing > > the name of the ForeignKey attribute -- in your case > > 'project' -- to another name. > > Lo and behold it actually worked ! > > Seems like magic :-)
Are you using a recent svn checkoutof the code? Because I'm pretty sure we fixed this problem last week. If you are seeing it with something less than a week old, it looks like we haven't quite nailed it. If you are using an older version, rest assured that in the latest code you could use the original names without conflict. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
