The source code was just tagged in the repository, so we can expect the final release being out in the next days!
Are you prepared for Firebird 3? The Migration Guide to Firebird 3 eBook is here to help you to move quickly to Firebird 3. The eBook is available in English and in Brazilian Portuguese.
The Portuguese version of my new eBook, Guia de migração para o Firebird 3 (Migration guide to Firebird 3) was just released! The book has tips and explanations to make the life of anyone who wishes to move to Firebird 3 easier.
An English version of the guide will be available in the following weeks at Amazon, both in paperback and digital formats. This is my third book devoted to Firebird, and the first one to be published also in English.
Brazilians can buy the guide right now in the FireBase on-line store.
Carlos H. Cantu
Sorry, for now, this is only for Brazilians…
Entrou no ar a campanha (crowdfunding) para financiamento do meu novo livro: “Guia de Migração para o Firebird 3”. Todas as informações e o formulário para contribuir estão disponíveis em www.firebase.com.br/guiafb3.php
Esse é um projeto totalmente independente, e depende de você para se tornar realidade! Dependendo de como for essa experiência, ela servirá de base para lançamentos futuros.
Acesse o link, leia e contribua se julgar interessante.
Carlos H. Cantu
The survey about Firebird 3 installer is closed, and results are now published (see below).
Thanks to everyone who participated and contributed with comments and ideas. I hope the result will help guiding the Project about what people expect/wants from the official installer 😉
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.
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.