Well now i noticed that there is a contest so here Firebird is mentioned and enters in the top 5 databases on Linux (Thanks to the Linux Journal readers)
Some Firebird Tricks for today
I’m a webmaster amongst other things for a significant web hosting provider.
I wanted to share some code and tricks I come across to pretend I’m knowledgeable, remember to not forget what I’ve learned and because I’m a little jealous of my colleague’s awesome blog.
Vote now in our new poll at FirebirdNews!
Just go to the MainPage and vote direct in the right sidebar. You can choose up to 3 answers.
Norman Dunbar is working in a new documentation describing some of the Firebird internals aspects, like the database file structure, compression used on records, etc.
The document is not finished, but already contains lots of good information.
You can download the currently version at:
Carlos wrote on firebird-php group : I’ve developed a stable version of a Firebird driver for the PHP Codeigniter Framework . Good feedback has been received from the Codeigniter community so far, and hope this could be useful for more developers working with PHP and Firebird.The sources are available at bitbucket here and any issues can be reported here
or at my blog here and for the English readers …
Thanx, live long and prosper…
Carlos García Trujillo
ps: seems that the driver is quite popular in such a small timeframe
I am happy that my driver for # firebird # codeigniter already are used by people from around the world in so little time:)
Now i have the clean build results and seems that clang++ is faster in one benchmark that i have tested Soon i will add more and test clang++ build with other benchmarks also some graphs will be added to the dry results 🙂
If you want to follow the clang++ build saga here is the tag on my blog
Some people doesn’t know, but anyone registered in the Firebird Tracker (registration is open, quick and free) can ask for improvements, report bugs, or vote in some existing tickets to raise their “priority”.
It is true that a high ranked ticket may never be implemented/solved. It is also true that the FB developers are free to implement what they want, without following any specific order or wishes. In fact, a ticket can be left untouched for a long time, if none of the developers feel inclined to work on that issue. But it is also true that having the users community voting for items, may sign to the Core Team developers with a direction to follow.
Here is a list of the top 10 ranked tickets at the moment:
Note that the top 10 issues are not bugs (the FB Core Team is a very efficient bug killer 😉 ), but enhancements/improvements to Firebird.
It seems that 775 and 657 are expected to be solved in Firebird 3. Core 773 and 2530 are related to the Firebird wire protocol.
Sadly, the top voted item (2530) is still unassigned. If you ever tried to use Firebird over the Internet and felt it is too slow, this is the issue you need to vote 😉 This improvement requires a new wire protocol, and changes to the API that would break the currently third-party access components. So, not easy task, but I hope to see it implemented in the future.