If you have ever worked with Firebird or Interbase using the standard .NET provider for OLE DB (System.Data.OleDb), you will have likely encountered issues like this:
The necessity to add ALL parameters manually.
Even though the OLE DB provider supports parameter generation for commands, the .NET provider doesn’t use it, so you as the programmer must do that work on your own.
The lack of support for named parameters. Although they actually exist, using them in reality requires a whole set of complex manipulations (the steps needed to add a parameter to a collection, etc.).
The impossibility of using multiple DataReader objects at the same time (Multiple Active Result Sets).
No execution of SQL scripts which contain several SQL expressions per command.
This list of difficulties a .NET developer has to deal with is far from complete.
Denys Khanzhiyev (node-firebird-libfbclient creator) wrote on nodejs mailing list:
I must admit your lib is faster than mine (See the response from Henry (node-firebird creator) , it is the result of the firebird library mode of operation : synchronous vs asynchronous mode of nodejs)
Concurrency Level: 5
Time taken for tests: 3.346934 seconds
Complete requests: 1000
Total transferred: 885000 bytes
HTML transferred: 821000 bytes
Requests per second: 298.78 [#/sec] (mean)
Time per request: 16.735 [ms] (mean)
Time per request: 3.347 [ms] (mean, across all concurrent requests)
Transfer rate: 258.15 [Kbytes/sec] received
node-firebird:
Concurrency Level: 5
Time taken for tests: 2.928723 seconds
Complete requests: 1000
Total transferred: 885000 bytes
HTML transferred: 821000 bytes
Requests per second: 341.45 [#/sec] (mean)
Time per request: 14.644 [ms] (mean)
Time per request: 2.929 [ms] (mean, across all concurrent requests)
Transfer rate: 295.01 [Kbytes/sec] received
Download links at the project’s page
New features:
Introducing Database structure comparison. This feature compares and generates stucture difference script of original database to compared one.
Include Views permissions in permissions management.
Many small modifications and bug fixes.
Even if running in the Classic (isolated process) mode, Firebird needs some data to be available to all the running server processes. There are four kinds of information that must be shared:
Lock table. It’s the vital part of the lock manager and its primary goal is to synchronize access to various resources that can be read or modified simultaneously.
Event table. Every time a posted event is committed, the server needs to find all the subscribers and redirect the event delivery to processes handling the appropriate user connections.
Monitoring snapshot. It keeps the latest known state of all the running worker processes and it gets updated once some user connection attempts to access the monitoring tables in a new transaction.
Trace configuration. It contains the information required for the worker processes to react on the currently active tracing events and log the appropriate notifications.