From: Preston L. <pla...@jo...> - 2004-01-15 18:33:18
|
On 15 Jan 2004, Patrick K. O'Brien wrote: > Preston Landers <pla...@jo...> writes: > > > By the way, my Sourceforge account is 'planders'. > > You are now a developer. Feel free to update the source files. I've > also given you release privileges, so that you can package up a file > release. Thank you very much for your contributions. They are > greatly appreciated. OK. I will work on that within the next week or so. I'm a bit tied up at the moment. 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. The only scenario I can think of where this change may break someone is if they were for some obscure reason relying on the warnings being raised as errors. |