MySQL sees an end for old databases
End of life for mysql 3.x and 4.0.x versions , time to switch to an better
alternative database system : firebird
(we have free source and binaries for all versions)
Here is the full article
End of life for mysql 3.x and 4.0.x versions , time to switch to an better
alternative database system : firebird
(we have free source and binaries for all versions)
Here is the full article
pabloj Moderator of Oracle and MsSQL forums at Devshed.com responded on Dimitry’s comments:
Hi, what follows are my personal thoughts after reading Dmitry Yemanov’s comments to a great poll posted at Firebirdnews about the features people would like to see implemented.
This is a great presentation, Jim throws in a lot of database history and insight into working with MySQL
Dan Letecky published an article about using embedded version of Firebird with .Net applications:
Firebird is a database with 20 years of history, full set of features (including transactions, stored procedures, hot-backup, excellent scalability, etc.) and a friendly open source license. It is an overlooked but compelling alternative to Microsoft Jet and Microsoft MSDE 2000/SQL Express 2005. Let’s take a look at how it can be used embedded in your desktop application. What makes Embedded Firebird ideal for embedding:
Read the full article here.
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.
Available here (you need to login to read the full interview).
The survey results are available at our website. A few participants may have not received the report as their email addresses were bouncing back.
I take this oppurtunity to welcome each one of you who did not participate in the survey to register at our website and download the Report.
Best regards,
Nitin
Ps. In case anyone would wish to take our latest survey on workplace harassment, please click here.
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
I have a HP Proliant ML350 with 2x80G HD (admitably bit of an overkill for my needs) which I am using as a file server for an office comprising of about 10 PC’s. Currently the OS is Fedora 4. I have firebird database running as the backend of a point of sale software.