On 11/7/06 2:26 PM, David Blewett wrote:
> Just wanted to jump on the band wagon. I've been using psycopg2 for ~6
> months now and haven't had an issue with it. I think this is a really
> valid point. We all know things are out of date as soon as they're
> printed, but this would be a real shame t
Gary Doades wrote:
> 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 o
On Nov 7, 2006, at 8:39 AM, 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_
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-Mo
I've been using it as well, no problems so far.
--~--~-~--~~~---~--~~
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
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 "
On 11/7/06, Gary Doades <[EMAIL PROTECTED]> wrote:
>
> I notice that the documentation is still recommending psycopg1 and not
> psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
> a while now. The psycopg site is now firmly recommending psycopg2 and
> noting that psycopg1 is e
In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I
think that this should be done.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
I notice that the documentation is still recommending psycopg1 and not
psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
a while now. The psycopg site is now firmly recommending psycopg2 and
noting that psycopg1 is effectively obsolete.
It may be better for the documentation,
