SQL DIFFs??? How.

[davood3]

here's the thing..

navicat DOES it.. however it doesn't give you the sql commands that it uses to do it.

I want to "capture" those commands as navicat does its dirty work so i can apply it to a different database than teh one navicat is working on.

I have been busy with work / exams recently. but tonight or tommorrow i will have time to spend more time smacking the log filing system around to see if i can generate some clean navicat logs with mysql server

I think the "update" logs are the ones I want right?

[quadroplex]

of course you know, saving your changes as you make them would be far simpler and take alot less time then hunting down a way to diff a sql file. I mean why would you make changes to your database without saving those changes somewhere other then inside your active db?

[quadroplex]

What I mean is I am making new zones in openzone, when I add them to the db i save sql files for each new zone, the spawns, doors zone, zonepoints, objects and so forth... Why didnt you do the same? What would happen if you had to totally reinstall everything? All that hard work would be gone forever leaving you at square one... Golden rule is Save Everything

[davood3]

to do that i'd need to do all my merchants and npc spawns via sql instead of the fancy tools or ingame convenience.

[quadroplex]

not if you do it then backup the table when your done with a simple where x = 'y' type of statement its not hard to backup things in mysql. I use fancy tools and ingame commands but I have current backups of everything I change, as long as you know the id or the name you can easily backup the information, even if you dont, you can just backup the entire table and restore it after you upgrade

[TheLieka]

Hindsight is 20/20, I suppose. We've had this problem as well in the past. We make our customizations with no intention of ever merging with another database, then suddenly - omg, something new and wonderful gets released in PEQ, so we have to go back and figure out what we've got vs what they've got - it's enough to make your head spin. For the record, we never we able to find an elegant way to do it.

If you turn on logging with the PEQ Editor, and only make your database modifications through it - it will generate a log file with all of the SQL statements for the changes that you make. If you don't have those logs though - I don't have any clue how to do it with the currently available tools.

Dax

[Theeper]

You could enable the general query log in MySQL when modifying the DB and then parse the INSERT, UPDATE and DELETE queries out.