Difference between revisions of "OpenDBX/Problems"

From Linuxnetworks
Jump to: navigation, search
(firebird and mysql problems)
 
(Sybase backend segfault on Windows plattforms)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Windows specific ==
+
== Common ==
  
−
=== MinGW ===
+
; 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.
  
−
; Firebird/Interbase backend doesn't find fbclient.dll : When adding -lfbclient as linker option, libtool complains that it can't find a valid library for -lfbclient. The workaround is to rename fbclient.dll to libfbclient.dll.
+
; 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.
  
−
; Firebird/Interbase backend doesn't link to libfbclient.dll : There's an issue regarding the __stdcall semantic of libfbclient.dll (function names are e.g. "isc_attach_database@24" instead of "isc_attach_database") which leads to unresolved symbols when trying to link the library. This might be either due to a missing .def file in the Firebird package or a problem of libtool which can't use the fbclient_ms.lib (or libfbclient_ms.lib after renaming) file when added as -lfbclient_ms.
+
== Windows ==
  
−
; MySQL backend creates a segfault at certain conditions : The MySQL backend compiles and links correctly but may create a segmentation fault depending on the libraries installed. It's not clear what libraries and versions are responsible for this problem.
+
; Sybase backend segfaults when using Sybase ASE libraries : The sybase backend doesn't work on Windows plattforms when used in combination with the Sybase ASE 15 libraries. It crashes for unknown reasons when trying to set up the message handlers, even if the code is exactly like in the Sybase documentation. The Sybase ASE 15 libraries work without problems on Linux/Unix systems compiling the same code base.

Latest revision as of 23:15, 22 March 2010

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.

Windows

Sybase backend segfaults when using Sybase ASE libraries 
The sybase backend doesn't work on Windows plattforms when used in combination with the Sybase ASE 15 libraries. It crashes for unknown reasons when trying to set up the message handlers, even if the code is exactly like in the Sybase documentation. The Sybase ASE 15 libraries work without problems on Linux/Unix systems compiling the same code base.
Retrieved from "https://www.linuxnetworks.de/doc/index.php?title=OpenDBX/Problems&oldid=3750"