[Fwd: [PYTHON DB-SIG] Jim's DBAPI proposelet]

[Michael Lorton]

>Hi.  I sent the attached proposelet a few days ago. Given recent
>discussions, I really thought It would generate some feedback, but 
>I haven't heard a peep.  This makes me wonder whether people actually
>got the message.  If a few of you would just acknowledge this
>note with private mail, I'll know that the communication lines are
>still working. :-)
>

I didn't see the first copy but maybe that was just me.  Points:

+ I don't see how you intend to store prepare statement
+ I don't understand how you distinguish "result set" from cursor (I
mean, I don't see both concepts separately embodied in code)
+ I think the datatypes (String, Number, Raw, and Date) are good and we
should keep 'em.
+ I think the exception model (OpError, ProgError, IntegrityError,
DataError) is good and we should keep it too.

To defend the last to points:
RDMSs' myriad fine distinctions among types (what is a tinyint vs. a
byte vs. a boolean?) is almost useless (IMHO); I cannot see why exposing
it to the user helps any.

While the programmer needs access to very specific error messages, the
program cannot be expected to understand the difference between (say)
Database Disconnect and Database Shutdown.  High-level catagory are much
more helpful.

M.


=================
DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org
=================