Am 31.12.2011 14:03, schrieb Ryan Chan:
Assume I am using InnoDB, which is ACID compliant.
Do I still need to use ECC RAM, in order to make sure there is no
chance of data corruption due data write?
define necessary
what has this to do with InnoDB / ACID
if the underlying hardware makes a
Ryan,
My opinion here.
Any write to memory can go wrong,
OS , MySQL , Storage engines, client library and so on.
Innodb has some advanced mechanism for ACID compliance like the double
write buffer but these are mostly to assure durability. Memory failure
although not so frequent can still, in my
On Sat, December 31, 2011 05:14, Claudio Nanni wrote:
Ryan,
My opinion here.
Any write to memory can go wrong,
OS , MySQL , Storage engines, client library and so on.
Innodb has some advanced mechanism for ACID compliance like the double
write buffer but these are mostly to assure
So then I try (in Mac OS X Terminal, while logged in as me (not root)):
mysqldump -uroot -p myDBname myTableName ~/myTestDumpedTable.sql
...and again it produces:
sh: mysqldump: command not found..
that is because Mac OSX is missing a package-managment and so you need
a little knowledge
Am 31.12.2011 23:53, schrieb Jan Steinman:
And for the record, there are at least two excellent package managers
available for Mac OS, and either MacPorts or Fink
if you call this package-managment from the view of a operating
system you have never seen a real one - this are ADDITIONAL
So then I try (in Mac OS X Terminal, while logged in as me (not root)):
mysqldump -uroot -p myDBname myTableName ~/myTestDumpedTable.sql
...and again it produces:
sh: mysqldump: command not found..
that is because Mac OSX is missing a package-managment and so you need
a little knowledge
