Bekende databases om grote hoeveelheden gegevens in op te slaan zijn natuurlijk de database van Oracle, de DB2-database van IBM en SQL Server van Microsoft. Een ander database management system is Firebird, dat de Interbase-database van Inprise als oorsprong heeft. Inprise is tegenwoordig bekend als Borland Software, waarvan de geschiedenis op deze pagina is na te lezen. Deze relationele database kan worden geïnstalleerd op verschillende besturingssystemen, waaronder het Linux- en het Windows-platform, waardoor het breed kan worden ingezet. Versie 2.5.6 van Firebird is uitgekomen met de volgende aanpassingen:
Firebird 2.5.6 Sub-release
This sub-release comes with a few bug fixes and a couple of improvements:Firebird 2.5.5 Sub-release
- Run-time errors raised inside EXECUTE BLOCK now provide the location context (line and column numbers). Backport from Firebird 3 by D. Yemanov. For more info, see Tracker ticket CORE-5216.
- Previously, when a restore failed to activate and recreate a deferred index, typically because of insufficient temporary disk space, gbak would return a non-zero completion code (“FAIL”) only when the failure affected a referential constraint. Now, gbak returns a fail code for any index that fails the activate-and-rebuild step. This improvement should be particularly helpful where backups and restores are managed using scripts, enabling indexes left inactive after the restore to be caught and corrected.
This sub-release comes with a moderate collection of bugs fixed over the past six months or so.
Vlad Khorsun's improvement for gbak in Firebird 3.0, producing run-time statistics in the verbose output, was backported to this v.2.5.5 sub-release. For more information, see Run-time Statistics in Verbose Output and SPB Support for New Statistics Feature in gbak Output.
One of Firebird's oldest bugs—CORE-214—was finally fixed: COUNT(DISTINCT ...) was too slow (until now!)
:strip_exif()/i/2001060653.png?f=thumbmedium)