Install problems.

[Tony]

I tried to install a test version of vb3.5.4 on a subdomain, I have setup a test database for this. I have my config file edited to reflect the test database. Both database's have the same user set to them.

Now I get to step 3 I think it was. It says a database already exists and click here will make make a new one and delete what you have.(something along those lines)

Well I go through with this step and it messed up my live database. How the heck could that of happen, Any Ideas?

Thank God I backuped my live database just before I did this!!! So I have my live site back running again. But I don't know what would cause this.

[Floris]

The user for this database doesn't matter, it are the unique database names.

databasename_one is not the same as databasename_two

I have no idea how this could have deleted the data from the live database (dbname_one) when you have pointed your config.php file to connect to the new database (dbname_two)

Perhaps you switched the name of the database and the db user around by accident?

[Tony]

I checked the config file like probably 4 times just to make sure I was using the right database. I get a little nervous sometimes when upgrading things, that's why I know I checked it and checked again.

Maybe I should just do a restore of the database on the testsite.


This is why I like the test site in a total different location of the live site, but that can't be done.

Is there a way to protect the database from being deleted?

I'm just happy you guys keep stressing the way you do to backup the database, It is cause of that why I backup before I do anything.

[Floris]

If you are sure the config.php of the test forum points to the test database you don't have to click the 'empty database' to continue.

I do recommend to set a unique table prefix in the config file, just in case it does use the other database for some reason. This way it won't overwrite existing tables from teh live site.

[Tony]

Thanks for the tip! So it would normally just start creating the tables.

How do I go about setting a unique table prefix in the config file?


Thanks for the help.

[Floris]

There's a config variable for table prefix in there, our online documentation has an exaple config.php file with information. http://www.vbulletin.com/docs/html/

[Tony]

I read the manual on this.

Just so I understand, all I need to do is edit the config file as specified with a table prefix of my liking for my live database. And that is it.

If I ever decide to change the prefix then I need some additional tools to do this. Not just editing the config file will change the prefix.

So what this does then is, when I install the test vb, vb will not recognize the database and only see the empty one.

Thanks again!

[Floris]

By default it is empty, you can set this to 'vbtest_' or 'anothervb_'


This means, when you do so one installed vb will have all the tables prefixed (or not) and another installed vb in the same database will have all the tables prefixed with vbtest_ or anothervb_

2 tables: from 2 installs

user
vbtest_user

[Tony]

So the two installs would be using the same database so to speak. There would end up being two databases in one.

I think I will pass on this, it sounds like something I would mess up.