In retrospect it is easier to make changes with an eye to the future. I know some folks around here, me included, that keep a custom.sql file that all db changes go into. That way you can (almost) always just drop your old db, source new db, source custom.sql and you're all set. Now if you didn't do that it's more difficult, depending on how much custom content you have. There is no diff for mysql dumps, unless someone has come up with one recently. I looked a few months ago and couldn't find anything. Depending on what changes have been made you can just plug the database updates into your current database and happily go right on. Then all you have to do is update your code. The downside to this is that there could be a lot of content changes in the PEQ db or AX db that you won't get.
|