> > does this also affect psycopg1? > > Looking at psycopg1 code, the answer would appear to be that it is not > affected. Changes to support Decimal appear to be psycopg2 specific. > > Graham
The problems I was seeing the other day were repeatable both using strictly psycopg1 (in fact, that was where I first saw the server error). The issue wrt Decimal is that the Django svn version uses Decimal and older versions use float, but because psycopg is "cached" it will convert it into the type that is initialized. In other words, its not psycopg itself - its the fact that it isn't re-initialized between requests. The recommendation I would make for now is that applications using new Django builds should use psycopg2 and applications using older builds should use psycopg1. This way there are two executables that don't clash in any way. I have done this myself and it eliminated all the problems I had with float/Decimal compatibility & Unicode. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
