On Tue, 2008-07-22 at 13:36 -0700, Steve wrote: > I ended up rebuilding everything with postgresql 8.29/pyscopg2.07 and > everything works fine. Email me if you have questions or a similar > problem as I never figured out why it didn't work with postgresql > 8.33. I'd like to know what the issue was.
Without knowing for sure what the problem was (your description was merely "behaves erratically", which lacks a little detail), I do know that there is some work we need to do w.r.t. Django and PostgreSQL 8.3. Prior to 8.3, PostgreSQL automatically did casting between fields of different types and now (8.3) it requires explicit casting. However, I would have thought that would show up as real exceptions, rather than silent failures. It certainly shows up as explicit tracebacks in the bug reports I've seen. 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 [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 -~----------~----~----~----~------~----~------~--~---
