Re: [opendbx] Error handling

2013-10-04 Thread Waters, Brian
mail list. Thanks, Brian. -Original Message- From: Norbert Sendetzky [mailto:norb...@linuxnetworks.de] Sent: Friday, October 04, 2013 12:08 PM To: OpenDBX devel list Subject: Re: [opendbx] Error handling -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brian > Thanks for the qu

Re: [opendbx] Error handling

2013-10-04 Thread Norbert Sendetzky
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brian > Thanks for the quick response. Below is the SQL statement that is > getting executed and below that is code. It appears that the > issue might revolve around the dbsqlok(). When dbsqlok() is called > in mssql_odbx_result() the following

Re: [opendbx] Error handling

2013-10-04 Thread Waters, Brian
} } catch (OpenDBX::Exception ex) { FTError *err = new FTError(FTError::Warning); err->setTextf("OpenDBX EXCEPTION: %s - %s", ex.what(), sql.c_str()); throw err; } } -Original Message----- From: Norbert Sendetzky [mailto:norb...@linuxnet

Re: [opendbx] Error handling

2013-10-04 Thread Norbert Sendetzky
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brian > We are considering using OpenDBX in a project that will access > mssql from linux. I am using the C++ API. I have a query that is > generating a primary key violation (severity 14), but the error is > not being surfaced. How should this