News from the Firebird developers.
The owners of the InterBase and Firebird Developer Magazine iBase.ru and IBPhoenix today agreed to collaborate in producing future issues of the magazine. Under the agreement, free copies of the magazine will be distributed to IBPhoenix Support and Subscription customers automatically in advance of publication.
Rails works with a wealth of web servers and databases. For web server, we recommend Apache or lighttpd, running either FastCGI or SCGI, or Mongrel. For database, you can use MySQL, PostgreSQL, SQLite, Oracle, SQL Server, DB2, or Firebird. Just about any operating system will do, but we recommend a ‘nix-based one for deployment.
[ED: spotted on the rails weblog and slashdot develannouncements]
An updated build of the .pkg file is at:
http://www.ibphoenix.com/downloads/Firebird-CS-2.0.pkg.zip
Right Click and Save As.
Fixed, problem with SET NAMES and loading character sets
Fixed, problem with loading UDFs
Regards
Paul Beach
There’s a new Null Guide beta at
http://www.firebirdsql.org/devel/doc/manual/temp/nullguide/nullguide.html
The following things have been added since the previous beta:
Developer Progress Reports for Core , DSQL , INTL & Security/Linux Builds (POSIX)
Dmitry Yemanov today posted to the Firebird-devel list his proposals for merging the Firebird 2 code with the Vulcan code. If you are interested in how it will be done and who will be doing it, subscribe to the list and watch the thread entitled “Merge Proposal”.
When is planned packaging of Firebird 2.0 ? Damyan responds:
Welcome to the 24th edition of Log Buffer, the weekly review of the database blogosphere.
From Dmitry Yemanov: As you might know, Firebird 2.0 no longer allows to alter/drop procedures that are used by active statements. However, we’ve got many requests from customers to restore the previous behaviour, because now it’s impossible to upgrade metadata under load. While we don’t consider this practice safe, I’d like to report that the new limitation is removed in the v2.0.1 release, thus rolling back to the prior logic. All potentially confusing situations (when two different versions of the procedure may coexist in memory simultaneously) are reported in firebird.log.
Curious about what you can expect from Firebird team in 2007? Check out the new official roadmap!
