Jim Starkey: Introducing Falcon (the video and the podcast)
This is a great presentation, Jim throws in a lot of database history and insight into working with MySQL
News from the Firebird developers.
This is a great presentation, Jim throws in a lot of database history and insight into working with MySQL
Getting back to some old ideas
Adriano dos Santos Fernandes has started a new brainstorming attempt targeted to the old subject of domains being used in procedure parameters and PSQL variables. He offers the prototype implementation and asks for comments. Possibilities to allow NOT NULL and CHECK constraints for parameters/variables are also being discussed. If you’re interested, please follow the discussion in the “firebird-architect” list.
Better error reporting
Did you ever debug a big complex procedure that fails in runtime with a famous “arithmetic exception” error? How much time did it take to find the problematic statement?
Now it should become much easier. Starting with v2.0, you get a stack trace which mentions the failed procedure/trigger along with all its callers. And the next (post-2.0) Firebird version will also report you the line and column numbers (inside the current PSQL body) of the failed statement.
Thanks to Eugene Putilin and Vlad Horsun for this contribution.
There are more than 500 votes already, so I think the current results are quite representative and hence they actually (more or less) reflect the features people would like to see implemented. Let me comment the top ones.
1. SMP support is a clear winner (23% of votes) in the poll. And this is definitely one of the high priority tasks in the project. As you know, it was the major goal of the Vulcan development and its implementation is being currently tested. The public test versions will be available soon for those who’s willing to test it in real-world scenarios. The final SMP implementation is targeted for the v3.0 release, as stated in our roadmap.
Read more
I have a FB server running on mipsel now – superserver debug version, in
a chroot over NFS, but anyway, it seems to work at first glance. I was
able to run the script to create our production database.
Is there any regression test I could try to run?
Best regards,
Fabrice Aeschbacher
There are two new members of the .NET Provider project:
Jiri Cincura: Will handle the nigthly build process for the .NET
Provider, DDEX, …
Le Roy Arnaud: Will be the mantainer of the ASP.NET Web Providers.
Weekly builds of FB ADO.NET Provider (only) are available on http://netprovider.cincura.net/ .
C# compiler from MS .NET FW 2.0 is used, builds using Mono, etc. will come too.
Comments and request are welcome and can be send to firebird-net-provider@lists.sourceforge.net (or to me/Carlos).
In order to provide additional/much needed functionality to assist in
tracking project issues, the existing SF Trackers are being replaced
with a new tracker based on the JIRA product
(http://www.atlassian.com/jira-bug-tracking/?edition=Enterprise). Read more
Dear developers
Microtec is pleased to announce a new version of CopyCat, our Delphi /
C++Builder component set for database replication.
CopyCat can be used for integrating replication functionality into your
applications, or for making your own customized replicators, enabling
off-site database work, asynchronous work over slow connections,
automatic live backup, etc.
For information about CopyCat, see http://www.microtec.fr/copycat/cc
For a list of changes in the latest version, see
http://www.microtec.fr/copycat/cc/Support.htm
—
Best regards,
Jonathan Neve
_______________
CopyTiger – advanced database replicator for Interbase/Firebird!
Web : http://www.microtec.fr/copycat/ct
_______________________________________
CopyCat – database replication components for Delphi/C++Builder!
Web : http://www.microtec.fr/copycat/cc
Devrace have recently acquired Metadataforge company (SQLHammer project) and will immediately start selling the product. Read details in the press-release.
From Dmitry Yemanov:
Implementation of the SQL-2003 compliant global temporary tables has been committed into the HEAD branch. This feature will be released in the next (post-v2.0) Firebird version. Design and implementation of the local temporary tables (both “defined” and “declared”, see the SQL specification for details) are being investigated, but there are no timeframes defined for that.