From: | Shaw Terwilliger <sterwill(at)sourcegear(dot)com> |
---|---|
To: | Joel Burton <jburton(at)scw(dot)org> |
Cc: | Marek P?tlicki <marpet(at)buy(dot)pl>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: pgsql for Python |
Date: | 2001-03-02 19:45:44 |
Message-ID: | 20010302134544.B6653@lister.sourcegear.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joel Burton wrote:
> PyGreSQL is more commonly used, and has (IMHO) a simpler, more dict-like
> interface, but isn't (AFAIK) thread-safe, nor DB API compliant.
I wrote a small web application server in python (www.lloop.com) using
Python and PyGreSQL. PyGreSQL was (mostly) thread safe, in practice, when
I started using it. I did a little bit of concurrency testing, found a few
uninitialized variables in the PyGreSQL module that caused crashes, but
these were easily fixed. If by thread-safe you mean a connection can be
safely shared between multiple concurrent threads, I don't know what to say
(never tried that). Pooling PyGreSQL connections and checking them in and
out to Python threads seemed to work well.
I haven't done much Python work lately, so I haven't tried PoPy (it sounds
nice).
--
Shaw Terwilliger <sterwill(at)sourcegear(dot)com>
SourceGear Corporation
217.356.0105 x 641
From | Date | Subject | |
---|---|---|---|
Next Message | adb | 2001-03-02 20:03:08 | Re: Re: serial properties |
Previous Message | Creager, Robert S | 2001-03-02 19:38:03 | RE: Slowdown problem when writing 1.7million records |