Author: mariuz

Adriano dos Santos Fernandes will push the pull requests from github mirror to svn repository
That way is easier to contribute to the project.

Tom Conlon added a Firebird NodeJS example of querying using asynchronous Promises.

Latest version for Node C++ Module for Firebird from git can be build on MacOSX fixing Linking flags (against regular Firebird installation)

Active Record Firebird Adapter 0.8.8 is updated with a few cleanups and fixes:
Merge pull request from Ray Zane : Use @config instead of @connection_params.
Fix sequence name limit.

Version 0.7.1 is on RubyGems now.
With following changes and bug fixes:
Fix naive rounding logic affecting negative scaled values.
Update for current rubygems, add license MIT like ar adapter , add rakefile.
Fixes error: ‘isc_info_db_SQL_dialect’ undeclared (first use in this function) replaced in Firebird 3.0 and marked as deprecated from firebird 1.5.

Sparx Systems now has a fully intergrated Firebird backend Database for its Enterprise Architect application

By default Firebird Classic package uses openbsd-inetd
You can inspect the config cat /etc/inetd.conf the max number of connections per minute is 255
after nowait you can suffix this field with a period, followed by the maximum number of connections authorized per minute for example nowait.10000
localhost:gds_db stream tcp nowait.10000 firebird /usr/sbin/tcpd /usr/sbin/fb_inet_server

To switch to xinetd an easier to use and popular alternative
sudo apt-get install xinetd
This will stop openbsd-inetd and will start xinetd alternative
You can inspect it with
cat /etc/xinetd.d/firebird25

There are a few issues with default config and it will be cleaned in the next firebird-classic package versions
A good config should look like this where i configured an unlimited numer of instances per source (also you can tweak the cps)

Download links and information on Jaybird wiki page

Dmitry Yemanov wrote on Firebird-Devel mailing list :

We’re getting closer to the v3.0 feature freeze which is going to happen
this summer. Everything roadmapped for v3 but not implemented before the
deadline will be postponed. The next-after-v3 release is likely to
incorporate most of the postponed features, but there may be new
features as well. So it makes sense to start discussing what could and
should be done in the next version(s). We have a few months to collect
the proposals, discuss technical details and make estimates about the
required efforts.

This message is the invitation to both project members and users who
closely follow the development. If you want to discuss something for
potentially including into the new version(s), feel free to do that in
separate threads. Please be prepared to protect your opinion and discuss
the details, simple votes “I like feature X” don’t count. A tracker
ticket for the feature request is appreciated, please add its URL to
your post.

Just for the reference, the top-voted tickets can be found here in jira

The ongoing results of the planning stage will be published on our
website and scheduled for the next version(s) by the project admins.

Dmitry