> > > I'm afraid I don't have any magic solutions. The best approach I can > suggest is to log the SQL that is being executed (either in the > Postgres query log or by putting in some debug statements into Django > to output connection.queries). Then narrow down the statement that is > causing problems by manually invoking the same SQL line by line until > you see the same error. > > Failing that, providing a minimal database dump that demonstrates the > problem may help others to replicate (and possibly solve) the problem.
I'll do some more sql inspection. It does look like someone has identified the models that may be causing the problem. For google data mining, the satchmo ticket is here - http://www.satchmoproject.com/trac/ticket/510 We'll look into it some more and try to get more specific about the issue. -Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
