https://bugzilla.novell.com/show_bug.cgi?id=739066 https://bugzilla.novell.com/show_bug.cgi?id=739066#c0 Summary: UnixODBC - SQLGetDiagRec() doubles all error messages returned by driver Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bdimm@hotneuron.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0.2) Gecko/20110902 Firefox/6.0.2 SeaMonkey/2.3.3 This bug was already fixed in UnixODBC version 2.2.13, which was released three years ago -- that was the conclusion after I exchanged several emails with the UnixODBC author to diagnose the problem. For some reason OpenSUSE 12.1 is shipping with UnixODBC version 2.2.12. Here is my original description of the bug: I've observed this bug with both MySQL and PostgreSQL on Linux, but not on Windows with MySQL, so I suspect it is a UnixODBC bug and not a driver bug. If I do a SQLExecDirect() with invalid SQL code, and then do: SQLINTEGER idx = 1; while (SQL_SUCCEEDED(SQLGetDiagRec(handle_type, handle, idx, ...) { [print error info] ++idx; } I see the error message printed twice instead of just once. Reproducible: Always Steps to Reproduce: 1. Write C code that calls SQLExecDirect() with invalid SQL code 2. Use SQLGetDiagRec() to print all resulting error messages 3. Actual Results: The error message describing the error in the SQL code is printed twice, i.e. two copies of the exact same error message. Expected Results: The error message should only be printed once. In the UnixODBC change log at http://www.unixodbc.org/ the fix for this problem is listed under the 2.2.13 release as: Fix problem with SQLGetDiagRec/Field returning double driver errors -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.