On 5/16/06, Bryan <[EMAIL PROTECTED]> wrote: > I talked with fog, one of the psycopg2 developers, about the current > state of psycopg2. He said that "psycopg 2 itself is stable right now" > and that they just need to complete zpsycopgda 2. From what's been > discussed, it doesn't sound like there is too much that psycopg2 can > change later on that would affect django if it decided to support it > right now.
That's good news -- thanks for the update. I just checked in a "postgresql_psycopg2" backend that uses psycopg2 with its psycopg1 compatibility layer. I have not tested this, so it probably doesn't work, but it's a start. One thing, for example, is that the register_type() syntax has changed in psycopg2. Please play around with the new backend and file tickets with patches that make it work! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
