I've recently converted from using MyISAM to InnoDB tables, and am pleased with InnoDB so far. However, the inability to use 'ALTER TABLE' with InnoDB tables is very problematic, as our software is still under heavy development and our database schema changes frequently. I'm working on a way to automate the drop/create/repopulate process to alter tables, but am running into a few problems:
Is there a way to prevent clients from noticing that the table in question is temporarily gone? Something like locking the entire database for writing? Second, mysqldump doesn't give foreign key constraints in its table creation commands. Is there any way to retrieve these? -- /----------------------------------------------------------- | Robert P Ricci <[EMAIL PROTECTED]> || <[EMAIL PROTECTED]> | Research Associate, University of Utah Flux Group | www.cs.utah.edu/flux || www.emulab.net \----------------------------------------------------------- --------------------------------------------------------------------- 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
