|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Walter Heck (lists
olindata.com)
Date: Sun Feb 01 2009 - 16:25:31 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
then: dump, import locally, rename and dump again. Still feels a bit
safer then parsing though it might be a bit more work.
OlinData: Professional services for MySQL
Support * Consulting * Administration
http://www.olindata.com
On Sun, Feb 1, 2009 at 9:42 PM, Robert D. Crawford <rdc1x
comcast.net> wrote:
> Walter Heck <lists
olindata.com> writes:
>
>> Might be a bit late,
>
> Better late than never.
>
>> but on the naming issue: why not rename the tables on the old database
>> before doing the dump? that would save you from potentially messing
>> with your data due to parsing problems.
>
> A good idea, but it wouldn't have worked for me. The original site was
> not mine and I didn't have permission to do so.
>
> Thanks,
> rdc>
> --
> Robert D. Crawford rdc1x
comcast.net
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=lists
olindata.com
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]