Firebird related news
New release for node-firebird fixes minor issue #70 :
Fix date parameter overflow :The used formula can result in negative time value (e.g.1938-12-29T17:00:00.000Z gives negative time) . In this case we need toadjust both date and time.
LINBIT, the leading provider of Linux based storage replication and disaster recovery, has announced the general availability release of its DRBD9 software. Developed to provide end-users, OEMs and ISVs a powerful tool to build redundant, highly scalable and flexible storage architectures, LINBIT’s new DRBD9 is the first replication design capable of connecting 30 nodes in real time to ensure data availability from multiple locations – even when disaster strikes.
New release for node-firebird fixes minor issue #69 :
Don’t try to read from an empty buffer
In some cases getSegment can get an empty (undefined) buffer which result to InternalError: "Cannot call method 'readUInt16LE' of undefined".
If you want to test apache with php 7 on windows here are the links
https://www.apachelounge.com/viewtopic.php?p=30718#30718
The firebird extensions are there, as you can see in
https://phpdev.toolsforresearch.com/php-7.0.0alpha1-nts-Win32-VC14-x64.htm
The first alpha for 7.0.0 was just released and can be downloaded from:
https://downloads.php.net/~ab/
The Windows binaries are available at
This is the start of a new PHP era! Thanks everyone who made and helped
to make this happen. From now on we are looking straight forward to get
the final in time.
Please test it carefully, and report any bugs in the bug system.
Alpha 2 will be tagged on Tuesday 23th and released on Thursday 25th.
Regards,
Kalle Sommer Nielsen, Anatol Belski and Ferenc Kovacs
Maximiliano Robain announced on django-firebird devel group :
Hi everyone,
I did just a little update on stable/1.6.x branch and a new release django-firebird v1.6.3. It includes a really minor fix on how catch and reraise exceptions and includes support for PEP 440 necessary to support PyPI updates.
The plan right now is to resume django 1.7 support (develop branch) and then continue with support for django 1.8 .
The idea is fix and close all open issues before merge it with master branch (now master branch == stable/1.6.x branch)
Any feedback is wellcome.
The web would never be the same :
http://php.net/manual/en/history.php.php
First Firebird / ibase driver was released with php version 3.0 (1998):
The incremental backup utility toolset nBackup is not a friendly beast. An operational misstep can break a database. Under load, in some conditions, it can be a database-killer without any human intervention, especially under Firebird v.2.1 or v.2.0.
There’s a proviso, though. A lot of the problem code was eliminated by a thorough revamp for Firebird 2.5. The threadability of attachments in v.2.5 is also thought to have reduced some of the instability of nBackup The improvements were not backported to the v.2.1 or 2.0 series because it was structurally infeasible.
This article is not a “How-to” for using nBackup. The Firebird Project documentation for proper use of this toolset is excellent and can be read or downloaded from the Documentation pages at the Firebird web site.
Smyatkin Maxim from RedSoft proposed the following changes in this pull request for Jaybird :
Jaybird shows horrible performance in auto-commit mode while executing
lots of small queries.
Reasons:
1. Every time a statement is being executed a new transaction starts and
commits.
2. Even if there were no changes at all (e.g., simple select statement)
Jaybird starts and commits transaction.
Solution: Firebird API has its own auto-commit flag. Firebird knows for
sure if anything did actually change, so Jaybird might rely on it. As a
result:
1. It saves start and commit calls;
2. It executes commits only if something really changed;
3. Internally it works faster even if changes appeared because it doesn’t
restart a transaction.
Practical results: it allowed me to make OpenCMS work 3-5 times faster
with Firebird. I suppose it’s not the only case, because some systems
(especially the ones using ORMs) tend to execute lots of small selects.
Main changes in code are:
1. Removed AutocommitTransactionCoordinator. LocalTransactionCoordinator
with enabled autoCommit flag does exactly what we need.
2. When we change autoCoommit to true/false – we commit previous
transaction manually, so that it restarts with new TPB.
