Difference between revisions of "OpenDBX/Problems"
From Linuxnetworks
< OpenDBX
(removed mingw problems => fixed in OpenDBX 1.4.3) |
(FreeTDS has problems with multiple statements) |
||
| Line 1: | Line 1: | ||
== Common == | == Common == | ||
| + | |||
| + | ; FreeTDS has problems with multiple statements : There seems to be a bug in the FreeTDS library at least up to FreeTDS 0.82 used by the mssql backend, when using first a SELECT and then a INSERT statement in one query string. The INSERT statement doesn't produce a result set in this case and you can't call odbx_rows_affected() for example. Linking the mssql backend against the compatible Sybase libsybdb.so works as excepted. | ||
; Oracle backend doesn't provide LOB functions : The large object handling functions are implemented but the Oracle backend doesn't offer them to applications. The necessary code in the oracle_odbx_result() functions isn't compiled as it segfaults when used. It's not clear why this happens and maybe a developer with more Oracle experience can make it work. | ; Oracle backend doesn't provide LOB functions : The large object handling functions are implemented but the Oracle backend doesn't offer them to applications. The necessary code in the oracle_odbx_result() functions isn't compiled as it segfaults when used. It's not clear why this happens and maybe a developer with more Oracle experience can make it work. | ||
Revision as of 13:09, 5 December 2009
Common
- FreeTDS has problems with multiple statements
- There seems to be a bug in the FreeTDS library at least up to FreeTDS 0.82 used by the mssql backend, when using first a SELECT and then a INSERT statement in one query string. The INSERT statement doesn't produce a result set in this case and you can't call odbx_rows_affected() for example. Linking the mssql backend against the compatible Sybase libsybdb.so works as excepted.
- Oracle backend doesn't provide LOB functions
- The large object handling functions are implemented but the Oracle backend doesn't offer them to applications. The necessary code in the oracle_odbx_result() functions isn't compiled as it segfaults when used. It's not clear why this happens and maybe a developer with more Oracle experience can make it work.
