Sinisa Milivojevic wrote: > As your entire discussion centers on the non-existence of NO DEFAULT, > I will briefly comment only on that.
I would like to add my support for NO DEFAULT. The lack of this feature is by far the worst thing about MySQL. > Forcing default on all columns is a design decision which had to be > forced for many reasons. Most important reason of all is that MyISAM > tables are designed for utter speed. Therefore, they are not > transactional tables nor do they have any form of pre-imaging. As on > the other hand, MySQL supports multi-row inserts (and soon even > multi-table updates), having defaults was a necessity as rolling back > upon hitting the error in user's data in N'th row is simply > impossible. I don't get this argument. What happens when a unique index is violated? Isn't this the same problem? --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
