> After developing on InstantDB as datasource for my CMP application I
would
> like to switch to MySQL because my application will also be deployed on
> Linux in the future. The newsgroup mentioned that MySQL should not be
used
> for serious applications. Often the complaints were not be able to have
> transactions. But a new stable version (3.23.32) is released and it
> supports transactions.
Never go to Usenet for counsel, for they will say both "Yes", and "No", and
"Me too!"[1]
There are several databases available for free (both as in speech, and as
in beer) on Linux - MySQL is not your only choice. To further muddy the
waters, both DB2 and Oracle are available if you feel like paying.
The most common alternative free database you'll find suggested is
PostgreSQL. "MySQL vs PostgreSQL" is the "emacs vs vi" perpetual floating
flamewar of the free database world.
MySQL was coded for speed and simplicity, and then started adding "real
database" features. PostgreSQL was coded to have the features, and speed
was only seriously worked on quite recently. Thus, MySQL supporters will
tell you that PostgreSQL is too slow and can't handle large objects
gracefully (both are no longer true), and PostgreSQL supporters will tell
you that MySQL lacks transaction support and that its table-level locking
makes concurrent access very slow unless the database is mostly read-only
(at least the first is no longer true).
At this precise moment, PostgreSQL probably wins out. A year or two ago,
MySQL was better. In six months time, who knows?
Charles Miller
[1] Not that this post is any improvement. :)
Consultant
Cirrus Technologies
t: +61 2 9299 3544
f: +61 2 9299 5950
Give me a compiler, and a star to steer her by.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
