Problems after upgrading from June to current release

Andrew80k · #1 02-12-2009, 01:23 AM

You've probably already backed up your database...I hope. The thing to do would be to restore your database. Then begin applying the changes that you see in the changelog but make sure you compare the changelog with the files in the utils/sql/svn directory so that you don't duplicate columns. You don't want to update something twice. I would go through the changelog, compare the changelog entry to the sql directory to see if there is a related change. Import that sql file or if there is no sql file, use the entry in the changelog. Sometimes if the change was pretty small it seems like an sql file didn't get created and just the entry in the changelog was made. Sometimes a reference in the changelog will point you to a sql file. Keep in mind there are a number of people making changes, and while I think they try to be consistent it doesn't always happen. Since you have a custom database it is going to be a little harder for you to get up to date and kind of painful. It will be well worth it. Any changes I make I keep in a custom.sql file that I can basically just import after I have made a database update. It's much easier that way. But that's harder to accomplish if you didn't do it from the start and don't remember all your customizations. Good luck. Let us know if we can help somehow.

gnode · #2 02-12-2009, 11:04 AM

It is only custom for itemization/spawns/npcs. I am doing all of this on a test/mirror server.

What you just suggested I do I have now done 3 times. Every single SQL reference in the changelog since my original install (a late june build) is in my update script. I also have included every single reference SQL file. Something is missing from the changelog, but I have no idea what.

gnode · #3 02-12-2009, 07:26 PM

Is there perhaps a master schema somewhere? I could just compare my DB to it and correct errors as I see them.

Andrew80k · #4 02-12-2009, 07:29 PM

I do think there is a schema in the Wiki, but I don't know how current it is. One thing you could do is just download a peq database from the CVS, load it into a different DB and then compare the 2. That might be faster than anything else.

gnode · #5 02-12-2009, 07:33 PM

Got a link? I originally installed peq off the distro from their website, but based on the filename at least (have not downloaded a 2nd time) it appears to be the same version I am still on, 1110

**cavedude** · #6 02-12-2009, 09:47 PM

Use the PEQ CVS. It is up to date.

gnode · #7 02-12-2009, 10:15 PM

Quote:

Originally Posted by cavedude

Use the PEQ CVS. It is up to date.

Ok I got your db downloaded and tried to import it to a new fresh empty db but got mysql errno 121 regarding foreign keys. Uninstalled mysql (was on 5.0.x) and downloading 5.1 to install and try again.....

Just keep getting road blocks :(