Problems after upgrading from June to current release

gnode · #1 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 · #2 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 · #3 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** · #4 02-12-2009, 09:47 PM

Use the PEQ CVS. It is up to date.

gnode · #5 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 :(

gnode · #6 02-12-2009, 10:24 PM

So, this is my game plan. Once I get the current PEQ db loaded and my recent backup db loaded, I am going to use this tool:
http://www.databasejournal.com/featu...l---SQLyog.htm

to bring my backup db's structure up to the same as the new peq db structure.

Then I am going to do all of the inserts in my existing db update script to fill in the necessary data from the updates.

Hope this works...

Andrew80k · #7 02-12-2009, 11:52 PM

You shouldn't need to upgrade your Mysql though. I've been using 5.0 for over a year and I've not had any issues. Let us know if we can help some way. Keep in mind it is hard for us to see what's going on so give as much detail as you can.