ODBC Interface version 07_01_0005, problem with C++ exceptions

From: Mister X <mister_ics(at)hotmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: ODBC Interface version 07_01_0005, problem with C++ exceptions
Date: 2001-06-14 06:06:42
Message-ID: HFQoOxQ14LD=I43R3kxo=+a04ABL@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-odbc

Hi,

developing in MFC/Visual Studio 6 I've encountered a strange problem
in last version of ODBC Driver (actually 07_01_0005). Each time a SQL
error occours, the istructions TRY/ CATCH doesn't report the error
string: the CDBException ' member m_strError is empty
Follows an example:

// MFC C++ Code

CDatabase myDB;

[.....] // Init and Open database...

//create a table with a WRONG SQL statement:

CString sSQLStatement="CREATE TABLE Dummy ( int DummyID, )";
// The statement is WRONG beacuse the comma
after the last column definition.

//Executes The statement and catch errors:

TRY
{
myDB.ExecuteSQL(sSQLStatement);
}
CATCH(CDBException, e)
{
AfxMessageBox(e->m_strError);
}
END_CATCH

Well, with driver version v06-50-0000 i got the string "Error
creating the table; ERROR: parser: parse error at or near ")", that
it is the correct error message from the back-end.
Instead, with Version 07_01_0005 of the ODBC driver, the string
e->m_strError is always empty, and the member m_nRetCode of
CDBException class is = -1;
Handling errors with C++ exception is a great thing, i thing this is a
bug of ODBC driver. The only way to discover the SQL errors reported
by the back-end is to analyze the driver connection log, after each
SQLExecute failed istruction, and it is not very very confortable for
the programmer :)

Thank you.

Silvio. mister_ics(at)hotmail(dot)com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-06-14 06:07:43 Segmentation fault in psql
Previous Message pgsql-bugs 2001-06-14 06:01:51 Strange CREATE VIEW behavior??

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2001-06-14 06:27:06 Error handling in ODBC
Previous Message Henshall, Stuart - WCP 2001-06-13 09:19:32 RE: ODBC+Access2000, Win2k and Win98