MySQL doesn't have the base necessary to provide real transaction handling. They have to add real logging and real row-level locking before they can support the higher level concept of transactions.
Forgive me but I don't agree to your explanation that MySQL doesn't provide "real" transaction.
Since the release version 3.23.54 of MySQL, there has been a very consistent and stable implementation
of support for Transaction.
If you really have used MySQL DB, you would of course implement the Standard version of it and
configure with either InnoDB or Berkely DB to provide support for transaction (PK and FK supports as well).
It's a not really a tedious for work for those who are accustomed to intalling, configuring, and using it.
That doesn't mean that they don't claim they do. But the bottom line is that real transactions require a real log, and I don't see it happening.
Using InnoDB or Berkely with MySQL, you would allocate log file size, path, and other pertinent settings
which are already included in some "my.cnf" files (but commented by default) and will depend on the
scalability requirements to which it will be implemented (enterprise, medium, small).
-- EDUARDO A. DELA ROSA "Anyone who has never made a mistake has never tried anything new." -- Albert Einstein |
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
