Hello Paul, I am only lobbying, not demanding.
Paul Dubois wrote: > Mmm, how do you know how much effort it would be? > Have you implemented it? Ok. IMHO it would be relatively easy for MySQL to implement, judging by my experience dealing with Monty and his source code (specifically, the myisam API). I await comments from MySQL AB. > Write a client that flushes all the tables, then places a write lock > on them all. That will keep anyone else from modifying them. Will it stop mysqld from reading them? Some maintenance processes such as myisamchk will actually move the files around, which could confuse mysqld. > Run myisamchk. When it's done, flush the tables again and unlock them. While that might be workable, don't you think the proposal would be both safer and simpler? Thanks, Stephen --------------------------------------------------------------------- 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
