Firebird Developer’s manual for Visual Studio .Net
IBProvider just released an on-line manual for using its own OLEDB driver to work with Firebird or InterBase databases in Visual Studio .Net.
IBProvider just released an on-line manual for using its own OLEDB driver to work with Firebird or InterBase databases in Visual Studio .Net.
here are the screenshots and connection string used for openoffice.org 2.4
here is a new portal for Turkish language speakers
How to enable firebird support in xampp
One of the most important new features in Plastic 2.0 is the distributed system. Today I’m going to talk about the set up I’m using to work from my laptop, disconnected from any network, and how I use the distributed system to synchronize changes back and forth.
Today, 2008-03-28, we published a 32bit-Intel-MacOSX port of FreeAdhocUDF ready for download. Many thanks to Paul Beach for helping and compiling.
Also, for special issues, a SuSe10-FireBird 1.5 port could be downloaded.
ADOdb is a PHP & Python database class library to provide more powerful abstractions for performing queries and managing databases. ADOdb also hides the differences between the different databases so you can easily switch dbs without changing code.
here is the release announcement and it does have support for firebird
you can vote and comment for firebird on download.com now
This Debian security advisory is a bit unusual. While it’s normally
our strict policy to backport security bugfixes to older releases, this
turned out to be infeasible for Firebird 1.5 due to large infrastructural
changes necessary to fix these issues. As a consequence security support
for Firebird 1.5 is hereby discontinued, leaving two options to
administrators running a Firebird database:
Posted in Firebird-Devel, by Dmitry Yemanov:
All,
The codebase will be tagged for Alpha 1 as soon as v2.0.4 RC1 and v2.1 Final are released. This means 10-15 days available to finalize the ODS changes and complete the major refactoring and synchronization efforts.
We expect only one Alpha version to be released. The next one will be Beta 1 which should be feature complete. No new ODS changes are allowed for Beta, unless some bugs would require fixing.
Besides the features already scheduled for v2.5 in the tracker, we have two features that the Foundation TTG (technical task group) has agreed to consider for this release during the Alpha stage: (1) tracing facility by Nickolay and (2) cross-database EXECUTE STATEMENT implementation by Vlad. They will be reviewed and discussed here soon, with an intention to be committed into the codebase before Beta.
Unfortunately, provided that the “external stored procedures” feature has major issues we still cannot resolve in the agreement (e.g. security and external engine API), it doesn’t seem to fit the v2.5 timeframe and is going to be postponed. Sad but true.
Comments anyone? We still have a bit of time to resolve your questions and adjust the release plan, if required. Just don’t forget that we want v2.5 to be a quick release and we’re already one month behind the schedule…
Dmitry