C++ NodeJS Firebird module will add soon Node 4.0 compatibility
Here is the pull request if you are in a hurry (tests do not pass yet).
Nan v2.0 or newer is needed to work with the new Node v4.0.
Here is the pull request if you are in a hurry (tests do not pass yet).
Nan v2.0 or newer is needed to work with the new Node v4.0.
Post by AlexeyKovyazin on habrahabr :
Many readers interested Firebird, may know that last year we saw releasead documentation on Firebird SQL language in Russian version 2.5.Creating documentation is sponsored the Moscow Stock Exchange as a platinum sponsor and one of the largest users of Firebird in Russia, and the company IBSurgeon / IBase, representing Firebird in Russia.
But this work is not over:
We began translating and proofreading of documents in English, German and Portuguese. Helen Borrie, the author of the famous Firebird book , is the editor of the English edition. We expect to publish the English version in October this year, Portuguese and German versions – early next year. At the same time in the Russian original documentation of 2.5 there were made over 1,000 corrections and additions (thanks to Denis Simonov, editor of the Russian version), as well as we conducted a lot of work on Reference documentation for version 3.0. We recommend to download an updated version of the Firebird 2.5 documentation in Russian and get acquainted with the beta version 3.0 documentation for Firebird: www.ib-aid.com/download/firebirdlangref30rus.pdf .If you find an error or typo in the documentation, do not hesitate and send bug-report directly to the Tracker for Russian developer documentation: www.assembla. com / spaces / firebird-russian-documentation / . In the Files group you can download the latest version of the documentation.

Firebird Project and the company IBSurgeon (IBase.ru) announced that Firebird SQL administrators and developers are invited to a free seminar on working with Big Firebird Databases. The workshop will be held on October 21, 2015 in Moscow. To participate in the seminar is by invitation only – see Below. Brief seminar topics:
Details here: ibase.ru/firebirdtour2016.html
Due to the limited places to visit you must get an invitation to the seminar. To receive an invitation, write to support@ibase.ru marked “Seminar BBD” and brief information about your company and the database (size, number of users, application area). If your database is larger than 500GB, you’ll definitely get a invitation if less, depending on availability.
This version will make the build reproducible.
The reproducible builds initiative aims to enable anyone to reproduce bit by bit identical binary packages from a given source, thus enabling anyone to independently verify that a binary matches the source code from which it was said it was derived. For example, this allow the users of Debian to rebuild packages and obtain exactly identical packages to the ones provided by the Debian repositories.
Prune tool sets the creation stamp in the database header to a fixed value (taken from the last changelog stanza) and
prunes unused space on index/data pages of shipped databases
Following the updated release of IBDAC (Delphi data access components for Firebird) Devart released a huge update of it’s dbExpress drivers. Among them you can find updated dbExpress driver for Firebird/Interbase.
Among many improvements and bug fixes those drivers received RAD Studio 10 support and now the trial limitation by 6 columns is removed from the Trial version for Win64 and it becomes a fully-functional Professional Edition.
You can already download new updated dbExpress driver for Firebird now – https://www.devart.com/dbx/interbase/download.html
Devart company released a huge update of all its Delphi data access components including Firebird/Interbase data access components (IBDAC).
IBDAC 5.6 main updates/fixes are:
You can already download new IBDAC 5.6 now and use it in your projects.
Jan Svoboda added initial Firebird Sql support to Redmine project management software.
Feedback is welcome.
At the 12th Firebird Developers Day, I talked about Using Firebird in high latency networks (aka. internet). Below are two slides from my presentation, where you can see the improvements in Firebird 3 wire protocol, compared to FB 2.5 and to MySQL.
Enjoy!
Obs: Left axis values are expressed in seconds. Test server was hosted in Amazon (USA) and client accessing it was located in Brazil. Ping reported latency of 219ms. The smaller the bar, the better.

Above graph shows the result of fetching 10.000 records from a real table used to store customers data. Red bars represents records with all the fields filled (ie: there was no fields containing nulls) and blue bars represents fetching records where some of the fields were nulls. Tests where done with and without compression.

The same table used in previous graph was created in MySQL InnoDB (same data). Blue bars means that wire compression was disabled, and red has compression enabled. Left side graphs has all fields filled (ie. there wasn’t null fields) and in right side graphs, some records has some null fields.
As you see, FB 3 won 😉
I should mention that there was no blob fields in the table, and this makes a lot of difference. Fetching non-null blobs makes the fetch slower in Firebird (more roundtrips are needed).
PS: The improvements in the FB 3 wire protocol were sponsored by donations collected in the 9th edition of FDD conference, and were implemented by Dmitry Yemanov. Compression was implemented by Alex Peshkov.