Teradata and 'SQL_ERROR or SQL_SUCCESS_WITH_INFO but no error reporting API found'
Daniel Kasak <[email protected]> Wed, 12 Mar 2014 17:42:17 +1100
| Newsgroups | gmane.comp.db.unixodbc.devel |
|---|---|
| Message-ID | <CAF73Y=RHWysb1YtPiw7DXW_nn+g5EZjFszMtPL-PdFhNOvNGrA@mail.gmail.com> |
--===============0051919781== Content-Type: multipart/alternative; boundary=001a11c35d1445a9e704f463234a --001a11c35d1445a9e704f463234a Content-Type: text/plain; charset=ISO-8859-1 Hi all. I have to connect to multiple databases via ODBC, so I *assume* I have to use unixODBC ( and not, for example, Teradata's driver manager). The problem is that Teradata's ODBC drivers appear to be pretty bad. If I execute a statement that works, everything is fine. But if I execute something that raises an error, I get: SQL_ERROR or SQL_SUCCESS_WITH_INFO but no error reporting API found I've googled for a while and found other people with the same issue, but no solution. What's going on here? Am I correct in assuming that Teradata simply haven't implemented an error reporting API? Dan --001a11c35d1445a9e704f463234a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi all.<div><br></div><div>I have to connect to multiple d= atabases via ODBC, so I *assume* I have to use unixODBC ( and not, for exam= ple, Teradata's driver manager). The problem is that Teradata's ODB= C drivers appear to be pretty bad. If I execute a statement that works, eve= rything is fine. But if I execute something that raises an error, I get:</d= iv> <div><br></div><div>SQL_ERROR or SQL_SUCCESS_WITH_INFO but no error reporti= ng API found<br></div><div><br></div><div>I've googled for a while and = found other people with the same issue, but no solution. What's going o= n here? Am I correct in assuming that Teradata simply haven't implement= ed an error reporting API?</div> <div><br>Dan</div></div> --001a11c35d1445a9e704f463234a-- --===============0051919781== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ unixODBC-dev mailing list [email protected] http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev --===============0051919781==--