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).

The report (with pictures) of the 9th edition of the Firebird Developers Day is now available (in English and Portuguese). Thanks for all attendees, speakers and sponsors! See you in next year, celebrating 10 years of the conference!

FireBase just published a test with 14 questions about general topics of Firebird RDBMS. Test is open and freely available to anyone registered at the site. Sorry but, for now, this is only for Portuguese speakers.

Many attendees of the 9th Firebird Developers Day donated money to sponsor the enhancement of the Firebird protocol, known to be “slow” in high latency networks (ie: internet). This is the #1 voted feature in the Firebird tracker! The development will be done by Dmitry Yemanov, chief of the Firebird development team, and available in Firebird 3 (with chances of being partially backported to Firebird 2.5.x). A list with the names of all donors and values can be found here.

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)

Second, the way as insert worked was deprecated. At previous versions we have contemplated not to use triggers for manage auto incremental fields, the value of autoinc fields were generated on python code by using GEN_ID or NEXT VALUE FOR according to firebird version. Now, is necessary to have triggers (and sequences/generators) for inserts and set new primary key values, then, if you are using a legacy database without this, It will not work.
If anybody think that is a bad idea remove this behavior and need it, we can discuss about it.

Third, obviously django-firebird doesn’t pass all the django test suite.
For example, django try to create a field as decimal(38,30)