Message-ID: <450AF14D.2030903@commandprompt.com>
Date: Fri, 15 Sep 2006 11:30:37 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
MIME-Version: 1.0
To: sdavis2@mail.nih.gov
CC: pgsql-interfaces@postgresql.org
Subject: Re: Python interfaces
References: <200609151352.20668.sdavis2@mail.nih.gov>
In-Reply-To: <200609151352.20668.sdavis2@mail.nih.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sean Davis wrote:
> I am in the process of moving development from perl to python.  Under perl, 
> there was DBI, the be-all-end-all of database interfaces.  Under python, 
> there is a plethora of options. 

Actually that isn't correct. The python drivers all adhere to DB API, 
the drives themselves are just a tad different. You can see the spec on 
DB API here:

http://www.python.org/dev/peps/pep-0249/


> Is there a recommended one for postgres?  It 
> will be mainly used in a web environment, so the ability to work 
> asynchronously is not that important.

We use psycopg2 for all python work.

Sincerely,

Joshua D. Drake


   I am interested in maintaining
> database introspection (which the DB-API 2.0 is conspicuously short on) 
> tools, as well as niceties such as automatic escape-quoting, etc, that are 
> pretty standard in perl.  Any suggestions?
> 
> Thanks,
> Sean
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
> 


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/