The Mystery of the RDB$DB_KEY in Firebird
Probably rdb$db_key is the best kept Firebird secret, because it gives the user some extra power to access records in raw mode.
Firebird related news
Probably rdb$db_key is the best kept Firebird secret, because it gives the user some extra power to access records in raw mode.
| Upscene Productions is excited to officially release FB TraceManager V3.5.0! |
Full Firebird 3 Alpha 2 support across the entire product (Trace API, header page monitoring, database statistics, monitoring tables), increased trace data fetch throughput and usability enhancements are some key facts about V3.5.0.
More information is available here:
http://upscene.com/displaynews.php?item=20140225
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.
News via via linkedin firebird group
Here you can find result of checking Firebird with PVS-Studio (in Russian).
And now the article is in English too
PVS-Studio is a static analyzer that detects errors in source code of C/C++/C++11 applications
Update: here is the Firebird-Devel discussion on the topic
Also the article is published in English
pyfirebirdsql Version 0.9.0 is released with experimental Firebird 3.0 SRP auth support
See the previous discussion on Firebird-devel list.
Here is the Firebird 3.0 example that works for me
Libreoffice new release with small fix for firebird sql driver fdo#74160 firebird XParameters::setString truncate to 65535 characters [Lionel Elie Mamane]
You can check release note here
https://wiki.documentfoundation.org/Releases/4.2.1/RC1
Thanks to assistance from Alex, we now have Firebird 3.0 building on MacOSX 10.8 with XCode 4.6.3
Regards
Paul
You can ask on firebird-devel list for the new builds
New release of IBPhoenix Replicator is capable to replicate data from Firebird,
Interbase and Oracle into any of these DBMS and into ODBC data sources as well.
There is long thread on increasing the passion in Firebird users (Or how can we improve the project).
Alternate threaded view is on gmane.
I liked this response about the long Firebird 3.0 release cycle
To be fair, V3 involved massive changes to the code base – breaking the server into pluggable
pieces so it can handle multiple versions without hugely complicating the code, plus fine grained
multi-threading, plus new security features essential for a contemporary database) and dozens
of other major features.There are more changes in Firebird V3 than any version I can think of since InterBase V1 to
InterBase V3 … maybe excepting V3 to V4 which added Windows support and SuperServer.
It’s an amazing feat for such a small group, and all the changes are critically important if Firebird
is to succeed in the next decade.Best regards,
Ann
Active Record Firebird Adapter 0.8.7 updated
Fixes regression affecting delayed_job usage :
When a result set is not returned, exec_query still needs to return the number of rows affected.
Active Record Firebird Adapter 0.8.6 now supports pluck for efficiently retrieving a single column of a result set in an array.
Another change is : Handle cases where sql does not return a result set.