[DB-SIG] spec: named parameters: clarification needed

[Kevin Jacobs]

On Mon, 17 Feb 2003, Anthony Tuininga wrote:
> > You should think of the DB API as a driver API specification not
> > an end-user interface.
> 
> I certainly have not thought so at all. The fact that you think so
> suggests that the DB API spec is not adequate for serious applications
> and wouldn't we want it to be?

DB-API for all of its short-comings is very well suited for serious
applications.  Unless, of course, syntactic sugar based on your particular
tastes have suddenly become a requirement.

Seriously...  get a grip.  There are _much_ more important things to argue
about than silly keyword arguments for a function that _everyone_ manages to
figure out.  If you don't like it, then fix it for your own applications. 
This is Python after all -- you're not stuck with a one-size-fits-all
solution.  

> -- in fact that's how I came to my understanding of the API
> because I found the specification misleading in places. So much for the
> official API.... :-)

Then work to clarify it, not arbitrarily permute parts that are generally
well understood.  If it matters that much, then put in the effort to help
define a community supported DB-API 3.0 that includes features that scratch
your itch.  However, you will want to take a serious look at what people are
doing with DB-API before you are judge yourself qualified to make such
pronouncements and expect to be taken seriously.

Just one author of "serious" applications built upon DB-API,
-Kevin
 
-- 
--
Kevin Jacobs
The OPAL Group - Enterprise Systems Architect
Voice: (216) 986-0710 x 19         E-mail: jacobs@theopalgroup.com
Fax:   (216) 986-0714              WWW:    http://www.theopalgroup.com