Hmm - usually the case of DBFAIL should be handeled by the following part, right after the call to dbresults: if ResultsRETCODE = DBFAIL then FDBLibConnection.CheckDBLibError(lcFetch, 'FETCHRESULTS/dbresults', IImmediatelyReleasable(FWeakImmediatRelPtr)); Do you have any chance to find out, why CheckDBLibError doesn't raise an exception?
Hmm - usually the case of DBFAIL should be handeled by the following part, right after the call to dbresults: ~~~ if ResultsRETCODE = DBFAIL then FDBLibConnection.CheckDBLibError(lcFetch, 'FETCHRESULTS/dbresults', IImmediatelyReleasable(FWeakImmediatRelPtr)); ~~~~ Do you have any chance to find out, why CheckDBLibError doesn't raise an exception?
Fix TZODBCClobW.Create to work if SQLGetData doesn't return MaxBufSize Bytes
Fix TZODBCClobW.Create to work if SQLGetData doesn't return MaxBufSize Bytes
merged revision(s) 8528 from branches/8.0-patches:
By @NickNevzorov: fix a problem in fetching clob data for ODBC.
Merged revisions 8516-8526 from branches/8.0-patches:
PR151 by rjackr: Fix Access Violation in BCD2SQLNumeric (ZDbcUtils.pas) when TBCD value is 0 via OLEDB