Actually, not tables--I'm utterly mistyping today--but the _server_ on which the database lies will almost always have a new name. (In theory, you could migrate the domain name of the dev MySQL server and avoid that rename, if you are hosting internally, but then you have no dev MySQL server for the next round of development. It is counterproductive to work in that manner.)
<br><br>ari<br><br><div><span class="gmail_quote">On 10/19/07, <b class="gmail_sendername">Ivan Sergio Borgonovo</b> <<a href="mailto:mail@webthatworks.it">mail@webthatworks.it</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 19 Oct 2007 14:24:23 -0400<br>"Ari Davidow" <<a href="mailto:aridavidow@gmail.com">aridavidow@gmail.com</a>> wrote:<br><br>> To totally nitpicky, I should have mentioned that the server on<br>> which your database resides will likely change its name (and your
<br>> tables may have to be renamed), so the setup fields where you put<br><br>Why tables renaming?<br><br><br><br>--<br>Ivan Sergio Borgonovo<br><a href="http://www.webthatworks.it">http://www.webthatworks.it</a><br><br>
--<br>[ Drupal support list | <a href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]<br></blockquote></div><br>