On Monday 11 May 2009 20:09:03 Karen Tracey wrote: > This was a PostgreSQL change with 8.3 that required modifying Django code > to account for the new behavior. See: > > http://code.djangoproject.com/ticket/6523
yes - this is it. I 'solved' the problem by removing the unique_together constraint. I can live with that. > > I think that was the main ticket that tracked it. Perhaps you can figure > out how to apply a similar change to your .90 level (I assume updating the > app to a supported level is not an option at the moment at least). yikes!! The app has worked for over 4 years - only requires minor tweaks now and then. If I had to upgrade, I would rewrite it and migrate the db. -- regards kg http://lawgon.livejournal.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
