Difference between revisions of "OpenDBX/Problems"
From Linuxnetworks
< OpenDBX
(firebird and mysql problems) |
(oracle lob issue) |
||
| Line 1: | Line 1: | ||
| + | == Common == | ||
| + | |||
| + | ; 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 specific == | == Windows specific == | ||
Revision as of 21:42, 9 August 2009
Common
- 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 specific
MinGW
- 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.
- 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.
- 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.