-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/01/07 07:31, Max Hyre wrote: > Roberto C. Sanchez wrote: >> On Wed, Jan 31, 2007 at 02:54:01PM -0900, Joshua J. Kugler wrote: >>> In that same document, they give the reason for doing so: >>> "The reason for using the preceding rules in non-strict >>> mode is that we can't check these conditions until the >>> statement has begun executing. We can't just roll back if >>> we encounter a problem after updating a few rows, because >>> the storage engine may not support rollback. The option >>> of terminating the statement is not that good; in this >>> case, the update would be ???half done,??? which is >>> probably the worst possible scenario. In this case, it's >>> better to ???do the best you can??? and then continue as >>> if nothing happened." >>> >>> >> I'm sorry, but "our database can't always handle >> transactions" is not a valid excuse for allowing bogus >> data. > > Does this mean that Mysql isn't really a DB, but is in fact just a > front-end, translating SQL statements into commands to the real DB?
MySQL with the MyISAM data store is *exactly* what you describe. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFwkKmS9HxQb37XmcRAgVHAKDBgwiyVWcCSl7jtMmQOSwJm/atnQCffXyS 4dkRg5saUcZFFEddkHGhfNw= =EwZz -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
