From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | sdavis2(at)mail(dot)nih(dot)gov |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Python interfaces |
Date: | 2006-09-15 18:30:37 |
Message-ID: | 450AF14D.2030903@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 2006-09-15 18:51:40 | Re: Python interfaces |
Previous Message | Sean Davis | 2006-09-15 17:52:20 | Python interfaces |