From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-interfaces(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL |
Date: | 2000-10-10 21:06:40 |
Message-ID: | 20507.971212000@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
"Billy G. Allie" <Bill(dot)Allie(at)mug(dot)org> writes:
> Peter Eisentraut wrote:
>> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
>> name, given that it's already used as an abbreviation for "PostgreSQL"?
> PgSQL is the name of the module you import in Python to access a PostgreSQL
> database from Python using the DB-API 2.0. The project name on SourceForge
> is "Python Interface to PostgreSQL". Of course, it there is too much heart
> burn with the modules name, I can change it.
FWIW, my initial reaction was the same as Peter's: that name is certain
to cause confusion. I don't want to try to force you to change it, but
I think it's not a good choice.
Don't have a better alternative to offer offhand, however.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-10-10 21:10:53 | Re: Re: [HACKERS] My new job |
Previous Message | Dave Smith | 2000-10-10 21:06:37 | Re: Re: [HACKERS] My new job |
From | Date | Subject | |
---|---|---|---|
Next Message | Billy G. Allie | 2000-10-10 21:42:42 | Re: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL |
Previous Message | Billy G. Allie | 2000-10-10 20:45:43 | Re: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL |