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 db as the back end. Steve. On Wed, Jan 28, 2009 at 6:14 PM, Robert D. Crawford <rd...@comcast.net>wrote: > Hello, Olaf, > > "Stein, Olaf" <olaf.st...@nationwidechildrens.org> 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 you have lots of > > tables or a huge dump file it might make sense to use a more automated > > approach, perl or python scripts will work on most platforms. The > > prefix will also make sure you have no naming conflicts I guess > > I figured that would be the case but I really needed to make sure. The > file is huge but judicious use of head, emacs, and cat should do the job > just fine without having to write something. > > One other question concerns these lines: > > CREATE DATABASE `db169254900`; > USE db169254900; > > I can just remove the CREATE DATABASE line and change the USE line to > reflect the name of the current db, right? > > Thanks for your help. My partner will be rather happy to have her wiki > up. > > rdc > -- > Robert D. Crawford rd...@comcast.net > > Laugh at your problems; everybody else does. > > >
