Category: Developer News

News from the Firebird developers.

New Flamerobin snapshot revision 2100 in #debian unstable

Leave a comment

The main change is that now it requires firebird2.5-dev instead of firebird3.0 headers and decided that is better to  have a flamerobin 0.9.3 in the distros released for the next 1-2 years with a stable firebird 2.5.x and add firebird 3.0 requirement when is ready and stable ~1-2 years
Changelog:
* New upstream SVN snapshot : revision 2100
* Uploaded to unstable
* Stop using system-wide ibase.h.Unstable has no fb3.0 so system-wide ibase.h has no boolean defines,which are used by FR and were ported to IBPP’s embedded copy of ibase.h
* build-depend on firebird2.5-dev instead of firebird-dev(firebird-dev is only in experimental)

You can download and install the package directly from debian sid (tested and works on ubuntu natty too )
http://packages.debian.org/sid/flamerobin
Also for ubuntu the install guide is now updated

Firebird PHP Generator 11.4 released

Leave a comment
Firebird PHP Generator SQL Maestro Group announces the release of Firebird PHP Generator 11.4, a frontend to generate feature-rich CRUD web applications for your Firebird database. The software comes in both Freeware and Professional editions.

New release introduces support for multi-level auto-complete editors, editing data within modal dialogs, improved client side validation and a lot of other useful things. There are also versions for other DBMS (MySQL, PostgreSQL, SQLite, Oracle, etc).

Read full press-release.

Firebird on Linux and ICU > 4.2

Leave a comment

Hi,

there was a bug in Firebird that did not handle well icu > 4.2 see (http://tracker.firebirdsql.org/browse/CORE-3447)

2.1.4 and 2.5.0 packages in distributions were affected (Debian, Fedora, Mandriva, Mageia) because they are using icu 4.4

Adriano fixed it and in these various distro updates are on the way

I know that some of you are using Centos 5.
The problem with Centos 5, is that you can’t have Firebird 2.5 from EPEL
repository. Centos 6 will give you the possibility to have Firebird 2.5 from EPEL6 repository, but seems that Centos6 take a long time to come.
https://www.centos.org/modules/newbb/viewtopic.php?topic_id=25878
http://wiki.centos.org/QaWiki/6/AuditStatus

You can try to use Scientific Linux instead (http://www.scientificlinux.org)
As Centos, the base SL distribution is basically Enterprise Linux
(RHEL), recompiled from source, and Scientific Linux 6.0 was released on
March 3, 2011
—
Philippe Makowski
http://www.ibphoenix.com

Change made to make Faster restores with gbak

Leave a comment

There is a simple change which makes restores much faster, tested with Linux 2.5 embedded restore
Two databases, with two different tables filled with 2,000,000 records:
create table t1 (n1 integer);
create table t10 (n1 integer, n2 integer, n3 integer, …, n10 integer);

----------------------
Restore timings:
T1: 14.5s
T10: 20.5s

Improved gbak timings:
T1: 9.7s
T10: 14.7s
----------------------

The good news is there is still room to improve the restore speeds , here is Adriano’s tweet:

I do have a slight different method, to insert 100K records in less than 1s over the same localhost method.

Also confirmed by the ending of the article:

PS: There is other restore improvement capable of take down time from
around 8.5s to 0.5s over TCP, but it still requires some analisys.

pyfirebirdsql will become the next Firebird Python driver

4 comments

Philippe Makowski wrote on the firebird-python list
The driver is hosted on github https://github.com/nakagami/pyfirebirdsql

First thanks Hajime Nakagami for your job

I really thinks that we need to put our effort on this driver so it became the Firebird Python driver instead of Kinterbasdb
here few points I saw :

– need a change in setup.py so install work
– transactions parameter we need the possibility to send custom transaction parameter buffers, for what I saw today transactions are (isc_tpb_write, isc_tpb_wait, isc_tpb_read_committed, isc_tpb_rec_version)
– need documentation
– can we extend it or create a new module to work with trace api ?

….

ps after a small change in setup.py I will certainly package it for
Mageia and Fedora

1 … 23 24 25 26 27 … 58