[DB-SIG] How to handle database warnings ?

[M.-A. Lemburg]

I am currently working on a modification to mxODBC which solves
the problems users sometimes have with database warnings. 
Since I think that some other database modules may have the 
same problem, I would like to get your opinion about this.

mxODBC currently converts most warnings from the database
into Python exceptions. This sometimes causes failure of
more complex operations like e.g. calling stored procedures.

To solve this, I've added a list attribute .messages to both
connection and cursor objects which will hold the error
and warning messages generated by the low-level code in the
order they are generated by the database. Errors will still be 
reported using Python exceptions, but I am planning
to drop the exception mechanism for warnings.

The latter will then only be available by looking at the
.messages list.

Now to make this easy and also to avoid the generation of
large message lists, I am thinking of auto-clearing the
.messages lists after prior to all method calls.

This would then enable code like:

   c.execute(sql)
   if c.messages:
      # got some warnings
      print c.messages
   for row in c.fetchall():
      ...

What do you think ?

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                        http://www.lemburg.com/python/