Re: MySql Vs Firebird
Firebird:
- clear and understandable SQL syntax
- fully supported relations
- multi generation architecture (but with incremental backups support)
- fully supported stored objects (procedures, triggers, UDFs)
- huge set of built-in functions
- fully supported transactions (including snapshot)
- autoincrement through sequence generators
MySQL (InnoDB engine):
- SQL syntax is really bad
- don't know MySQL's architecture
- transactions may work
- huge set of built-in functions including stupid limitations when using them (CURRENT_TIMESTAMP can't be used in columns of type other than TIMESTAMP (e.g. DATETIME) and also there cannot be more than 1 TIMESTAMP columns with NOT NULL constraint in 1 table - what a stupidity)
- stored objects support is practically missing (except really bad stored procedure/function)
- autoincrement values support is really bad
In my opinion - MySQL is the worse (pseudo)SQL server I've ever seen. Hopefully there will be soon available spatial support for Firebird & MySQL will be kicked out really fast. MySQL can't be used for serious development.
M.T.
Subject
Views
Written By
Posted
29884
October 21, 2008 04:33AM
Re: MySql Vs Firebird
15826
November 26, 2008 03:47AM
16990
January 16, 2009 10:34AM
13644
March 06, 2009 06:58PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.