[PyDB2-discuss] Re: I have a patch to handle SQL_SUCCESS_WITH_INFO

[Preston L. <pla...@jo...>]

On Fri, 16 Jan 2004, ??? wrote:

> > Does anyone have an issue with the solution that I chose to handle the
> > SQL_SUCCESS_WITH_INFO state?  To remind you, that is the case where an
> > operation worked (e.g. returned rows) and yet there is a warning string
> > from the database server.   The solution I chose was just to stuff the
> > warning string into a LastWarningString attribute of the cursor object and
> > rely on the caller to check the string if they care.  Previously, the
> > driver was raising the warning as if it were a fatal error
> 

> Personally, i'm reluctant to add a new ``public'' attribute to cursor
> object for being used by users. Because PyDB2 users get stucked with
> the attribute once it is provided as public attribute.
> 
> And the best solution is to use ``warning'' module to control warning
> situations in standard manner. Could you please consider warning
> module solution? Adding internal attribute is OK and the attribute
> SHOULD be controlled by DB2.py.


Hello, thanks for the response.

I'm not sure I understand what you mean by a 'warning module.'  Perhaps I
don't know what the standard manner is.  Can you please provide an example
of another Python module that does it that way so I can refer to that?

thanks,

---
Preston Landers - pla...@jo...
Senior Software Developer, Journyx, Inc.
Austin, Texas  (512) 225-3929