Robert,
I know you have had other answers, but as to the database name, yes, you can
remove the CREATE DATABASE statement and change the USE statement to the
right database name.
N.B. In our environment the students have only one database each, and will
install blogs and wiki's etc. using that one
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 wrote:
> Walter
Walter Heck 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
Might be a bit late, 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.
Just a thought :)
Walter
OlinData: Professional services for MySQL
Support * Consulting * Admini
Olaf Stein writes:
> I think he only has one DB, I guess that is a provider restriction...
True. I would create a separate db for each application if I could.
rdc
--
Robert D. Crawford rd...@comcast.net
--
MySQL General Mailing List
For list archives:
I think he only has one DB, I guess that is a provider restriction...
On 1/30/09 8:52 AM, "Claudio Nanni" wrote:
> Robert,
>
> keep the two databases separated,
>
> that is on different mysql database (or schema as they are also called).
>
> If the wordpress blog is on a database named 'wpbl
Robert,
keep the two databases separated,
that is on different mysql database (or schema as they are also called).
If the wordpress blog is on a database named 'wpblog' for example
import your dump in another newly created database.
Could just use those statement in the dump file
CREATE DATAB
Hello, Olaf,
"Stein, Olaf" writes:
> the import of the dump will not remove your other tables unless there
> is a naming conflict, then the table will be overwritten. As far as
> the prefix goes you can edit the dump file, find the create table
> statement for each table and add the prefix. If y
Robert,
the import of the dump will not remove your other tables unless there is a
naming conflict, then the table will be overwritten. As far as the prefix goes
you can edit the dump file, find the create table statement for each table and
add the prefix. If you have lots of tables or a huge d
