Category: General news

The libjaybird22.so (Linux x86) and libjaybird22_64.so (Linux x64)
included in the Jaybird 2.2.0 download are incorrectly linked (libstdc++
and libdl are missing from the symbol table).

This manifests itself when the native or embedded protocol is used
(jdbc:firebirdsql:native or jdbc:firebirdsql:embedded). The resulting
error is UnsatisfiedLinkError occurs in libjaybird22_x64.so undefined
symbol: _ZTVN10__cxxabiv117__class_type_infoE

This error does not occur on all systems (eg my Ubuntu 11.10 systems
with the OpenJDK-6 and OpenJDK-7 from the Ubuntu-repository don’t have
this error).

Correctly linked versions of libjaybird are attached to
http://tracker.firebirdsql.org/browse/JDBC-259

The next release of Jaybird will include correctly linked versions of
this library (release date is not yet known).

Short answer is FDB
The difference between FDB and kInterbasDB is explained here

It’s old and unmaintained , all effort is on FDB driver and it is backward compatible with kInterbasDB
Now between FDB and FirebirdSQL , from what i know pyFirebirdSQL is pure python so it can work without any other so/dll installed and it can be used for example in places where there is no Firebird client installed (think of android python script)

The article is in Spanish from the Django Firebird driver maintainer

The option in the config is removed

 

Prior to Firebird 2.5 the SET clause of the UPDATE statement assigned columns in the user-defined order with the NEW column values being immediately accessible to the subsequent assignments. This did not conform to the SQL standard. Starting with Firebird 2.5, only OLD column values are accessible to all the assignments of the SET clause.

Example of the old vs new behaviour:

UPDATE T SET A = B, B = A

old result: A gets equal to B, B doesn’t change

new result: A and B get their values exchanged

Change this configuration option to 1 (true) only if your SQL code relies on the legacy semantics of the SET clause. It’s provided as a temporary solution for backward compatibility issues and is removed in Firebird 3.0
Type: boolean

OldSetClauseSemantics = 0

Posted in FB-DEVEL:

FIrebird for Android
——————–

Key: CORE-3885
URL: http://tracker.firebirdsql.org/browse/CORE-3885
Project: Firebird Core
Issue Type: Task
Components: Build Issues / Porting
Affects Versions: 2.1.5
Environment: Android 4
Reporter: JLM
Priority: Minor

Hello,

I’m trying to build Firebird 2.1 for Android ARM.
For the moment, I am compiling, step by step, by correcting builds issues.
To compile, I use the custom NDK R7 by Crystax in order to use the standard libc instead of the Bionic libc.

I will write my advance gradually.

Regards,
Loweno

Do you have interest? Vote for it in the tracker and show your support  😉

Highlights for this release:

• – Support for Firebird stream BLOBs (see ReleaseNotes for details)
• – Fix for PYFB-17 and PYFB-18 (see our JIRA tracker for details)
• – Fixes for automatic unicode conversions + refactoring
• – Some optimizations
• – Documentation (stub, from KInterbasDB 3.3.0)

Target for next release: Documentation