SQL problem on install

registered · Regular Joined: Sep 11, 2005 Posts: 54 Location: Sweden

Hi guy's

Did a new install yesturday using the same database as one of my other sites use.

I configured config.php to add "shop" as prefix to separate the new tables from the existing called "nuke".

Then I ran the InstallSQL.php.

As stated in the istaller the tables are replaced and they certainly was Crying or Very sad

The new tables was installed prefixed as "nuke" even though config.php said "shop".

Now to my question.

Is this correct?
Is it possible to make a new install using the installer and use an existing database and separate the tables with the prefix-comand in config.php?

Unfortunatly I was to eager to get the new site upp and running so I made no backup of the old site which now is gone, gone, gone Crying or Very sad

Oh, well s**t happens, but I'd like some input on how things work, or should work.

Cheers / B

Posted: Fri Jul 28, 2006 4:42 am

Unfortunitly it looks like the installer uses the prefix nuke and does not call from the prefix set in config.php.

I am currently on my way to work, but I will make the installer call from the $prefix from config.php and post a link to get the altered copies.

Others may have already developed such an installer. Either way, this is not a complicated scenerio, Just a lot of edits to make Laughing

No worries, well have it for you asap.

Sells PC To Pay For Divorce Joined: Posts: 5661

well couldnt you grab the tables from the db and do mass replace of nuke_ to shop_ ?
just a thought..,if thats what you wanted...

Posted: Fri Jul 28, 2006 4:55 am

Thx!
No worries, I just wish I had such an installer before i lost my old tables Smile

Have a good day at work!

Cheers / B

Posted: Fri Jul 28, 2006 4:58 am

hitwalker wrote:

well couldnt you grab the tables from the db and do mass replace of nuke_ to shop_ ?
just a thought..,if thats what you wanted...

Yes i guess I could, but its to late now Wink

Old tableas are gone.

I just wanted to know how the installer workes and if that is the correct way...

I figure that if you have the prefix attribute in config.php you might as well use it...
Twisted Evil

Cheers / B

registered · Posted: Fri Jul 28, 2006 7:39 am

Quote:

Unfortunitly it looks like the installer uses the prefix nuke and does not call from the prefix set in config.php.

Well, 2.10.00 was modified to do this already and the installer is copyrighted by Raven and he requests that it not be distributed (per his comments in the script).

Posted: Fri Jul 28, 2006 7:50 am

The problem you reference (using Nuke instead of $prefix) was corrected in the version that's under development on May 1. Unfortunately the version that's currently available for download was generated before May 1 so the bug is still in there.

Code in the old version reads like this:

Code:

DROP TABLE IF EXISTS `nuke_authors`;


CREATE TABLE `nuke_authors` ( `aid` varchar(25)  bla bla bla

Whereas code in the new verison reads like:

Code:

DROP TABLE IF EXISTS $prefix.`_authors`;


CREATE TABLE IF NOT EXISTS $prefix.`_authors` ( `aid`

Unless this "fix" can be "backported" you are stuck with this until 2.10 is released. The problem is that backporting would require retesting and making sure that other things aren't unglued and would divert attention from getting the new release out the door. You could I suppose, armed with the knowledge dispensed here make global changes to the files in the SQL directory under the INSTALLATION directory of the 2.02 distribution.

Posted: Fri Jul 28, 2006 8:40 am

Well I see you guys have the problam containded and under controll, I will wait "some more" for the .10 release....-and lick my wounds from the disater last night.

Keep up the good work!

Cheers / B