I believe that MySQL achieves some measure of ACID compliance if the
db manager(s) choose to apply Inno DB tables.
In which case does the following business news (as says MySQL)
"validate" the approach, or does it represent another good reason to
be using PostgreSQL?
http://www.ecommercetimes.com/story/Kp6ts4bb9Qqbla/Oracle-Puts-Squeeze-on-MySQL-With-Latest-Buy.xhtml
At 6:18 PM +0200 10/10/05, Karsten Hilbert wrote:
On Fri, Sep 30, 2005 at 01:53:12AM +0200, Hilbert, Sebastian wrote:
This information is what really counts. Though noone explicetly
asked you one
cannot be expected to know this. To make this thread worth the words that
have been spent on this would you mind giving us some inside on why MySQL is
not a good idea.
Here:
> database that's truncating integers and neither enforces
> ACID compliance ?
What this means is that MySQL does not enforce integrity of
the data as much as it should.
I still don't see what would make php a bad option for the web interface
It is not at all. PHP is perfectly fine.
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
