Firebird Language basic Reference ready This Year

Paul Vinkenoog wrote on firebird docs list

This is just to let you know that I’m making time available for the Language Reference this year. I’m working on the DML chapter now, and I’m somewhere in the middle of the SELECT statement. All the others are finished (the other DML statements, that is – not the other chapters!)

I will do my utmost to have a “basic” Language Reference ready this year, i.e. possibly without all the details on Dialect 1 and other things that people can hopefully live without for a while (or grab the IB6 LangRef if they can’t).

Once finished, updating it to Firebird 3 shouldn’t be a hell of a job.

But it ain’t finished yet.

Redsoft Database (based on Firebird) used in GosLinux systems for FSSP

Management of Information Technology of the Federal Bailiff Service (FSSP) Russia announced a new phase of implementation of the free software and “import information technology” – the appearance of their own GNU / Linux distribution called GosLinux.

GosLinux distribution is based on CentOS 6.4 and created by “Soft Red” in 2013 after a win of the Russian company in the competition for revision, implementation and maintenance of automated information systems for FSSP Russia. In the server infrastructure of the territorial distribution of the FSSP Russia CentOS was used since 2012, and now all units bailiff service can use a specialized system, which received a FSTEC certificate at the end of March.

Among the major software components of the distribution used in the FSSP Russia, referred to the : Apache Tomcat application server and “Red Soft” database based on relational open source database Firebird.

And another article here
ps: Sorry for google translation

FB TraceManager V3.5.1 has been released

FBTM_V3_48x48 Upscene Productions is excited to officially release FB TraceManager V3.5.1!


This release adds support for pre-defined purge options of stored trace data. Minor issues have been fixed as well.

More information is available here:
http://www.upscene.com/displaynews.php?item=20140407

Or also directly in the V3.5 what’s new section of the online product documentation:
http://www.upscene.com/documentation/fbtm3/index.html?whats_new_in_v3_5.htm

More information on the product is available in the FB TraceManager section on our website, including an edition comparison sheet, webcasts etc.:
http://www.upscene.com/go/?go=fbtm

Thanks for your continued support.

How to patch, build and debug PHP extension : PDO Firebird

Vjacheslav V. Borisov wrote a tutorial on how to build and debug PDO Firebird driver :

I noticed that there is too many bugs open and too few developers who can
do the work.
And even this list is almost dead. Don’t know what is the cause of that,
but may be it is just hard to start ?
I recently written some patches for php – work, which I never done before.
And i can say, this really not so hard, if you know C/C++ (or at least
php?) and linux.
Most troublesome work is to setup build environment, so i decided to write
instruction how to patch, build and debug PHP extension, so may be more web
developers can contribute to php.

Advanced Solutions How to : Coordinating transactions for multiple connections in single call

Leyne, Sean asked on Firebird-devel
(You can read in that thread the details about problem requirements and proposed solutions)

Consider a large database (200GB, large tables with 450 Million rows) which is running on a kick-a** server
with pool of enterprise SSDs for storage (more IOPS then Firebird could ever use), which I need to extract
data from on a regular basis throughout the day for use by an external BI system. During the business day,
the database is Live with over 300 connections active with 1 million+ DB transactions.

I need to extract the BI data as a true “snapshot” of data (ensuring FKs are valid), in as short a timeframe as possible.

Because runtime is critical, I want to break the extract process into logical pieces and run each piece is a
separate process/thread (with its own connection) (aka run in parallel).

1 97 98 99 100 101 200