Yeah, I've been using it for a couple of months now with no problems. I also use it on another project via SQLAlchemy.
I only really pointed it out when I saw the beta chapters (chapter 2) for the book. If it still recommends psycopg1 when it comes out it may look out of date. Jacob Kaplan-Moss wrote: > On 11/6/06 6:28 PM, orestis wrote: >> In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I >> think that this should be done. > > Indeed I am; it works just fine. > > For now, I'd just suggest using the "postgresql_psycopg2" backend. At some > point, we should probably rename that one "postgresql" and rename the old one > "postgresql_psycopg1" just in case people still need it. > > Jacob > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
