[DB-SIG] DB API 1.1a3

Jim Fulton jim.fulton@Digicool.com
Wed, 01 Jul 1998 17:32:06 -0400

M.-A. Lemburg wrote:
> Tod Olson wrote:
> >
> > >>>>> "M" == M -A Lemburg <mal@lemburg.com> writes:
> >
> > M> I've uploaded a new edited version of the API 1.1 specification. It
> > M> includes most of the things and modifications we have discussed in
> > M> the past weeks (I probably forgot some):
> >
> > M>         http://starship.skyport.net/~lemburg/DatabaseAPI-1.1.html
> >
> > M> Comments ?
> >
> > I notice that 1.1 no longer requires Connection objects to implement
> > all Cursor object attributes and methods.  Any reason?  I would like
> > the requirement to remain.
> Is anybody using this ?

I find it very annoying to have to support this.  It is crudifying a
DBI module I'm working on. Ick.

> I think it's a better idea to provide a
> dummy cursor object than having connection objects give access to
> cursor methods and attributes: it makes porting applications a lot
> easier. Database interfaces which do not really support cursors
> could raise an exception if more than one cursor is being created.
> But that's of course just my POV.

I agree.

(Actually, I don't like the DBI-API's exposed cursor interface, but
 given it, I agree. :)


Jim Fulton           mailto:jim@digicool.com
Technical Director   (888) 344-4332              Python Powered!
Digital Creations    http://www.digicool.com     http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for