Message-Id: <200010102142.e9ALggk28981@bajor.mug.org>
From: "Billy G. Allie" <Bill.Allie@mug.org>
Reply-To: "Billy G. Allie" <Bill.Allie@mug.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-interfaces@postgresql.org,
	pgsql-hackers@postgresql.org
Subject: Re: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant
	interface to PostgreSQL
In-reply-to: Your message of "Tue, 10 Oct 2000 17:06:40 EDT."
	<20507.971212000@sss.pgh.pa.us>
Date: Tue, 10 Oct 2000 17:42:42 -0400

Tom Lane wrote:
> "Billy G. Allie" <Bill.Allie@mug.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

I couldn't think of a better alternative, either.  That's why the module
name is PgSQL.  Of course, seeing 'import PgSQL' in the python code seems
to imply loading code to access PostgreSQL.  It's kind of self-documenting,
don'y you think? :-)


I am, however, open to suggestions to a better alternative if one can be
offered.


I am, however, open to suggestions to a better alternative if one can be
offered.
___________________________________________________________________________
____       | Billy G. Allie    | Domain....: Bill.Allie@mug.org
|  /|      | 7436 Hartwell     | Compuserve: 76337,2061
|-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie@email.msn.com
|/  |LLIE  | (313) 582-1540    |