[DiscordArchive] <@772737304400887838> couldnt he just open his backup with a text editor and then use find & replace
[DiscordArchive] <@772737304400887838> couldnt he just open his backup with a text editor and then use find & replace
Original source
<@772737304400887838> couldnt he just open his backup with a text editor and then use find & replace to find all instances of `INSERT INTO` and change them to `REPLACE INTO` and then run worldserver and authserver to build the tables and populate them, then run his backup to replace things with his backup?
i mean i guess the issue would be that if his old db and new db are on different updates, then there could be some issues, but could also just clear out the updates from the update table up to where his old version was from so it reapplies them?
rektbyfaith
09-16-2025, 07:20 AM #1Archived author: Mithria • Posted: 2025-09-16T07:20:14.495000+00:00
Original source
<@772737304400887838> couldnt he just open his backup with a text editor and then use find & replace to find all instances of `INSERT INTO` and change them to `REPLACE INTO` and then run worldserver and authserver to build the tables and populate them, then run his backup to replace things with his backup?
i mean i guess the issue would be that if his old db and new db are on different updates, then there could be some issues, but could also just clear out the updates from the update table up to where his old version was from so it reapplies them?
Original source
Good point, that does make sense on both counts. I think it should work with preventing the updates that came after the export from running until after the import.
Something else to deal with will be whatever custom spells and possibly items they added, assuming those are mentioned in the character entries who had them at the time and the old DBCs aren't being used now. I'm guessing that'll just be warnings from them not existing, though.
rektbyfaith
09-16-2025, 07:24 AM #2Archived author: Spargel • Posted: 2025-09-16T07:24:27.521000+00:00
Original source
Good point, that does make sense on both counts. I think it should work with preventing the updates that came after the export from running until after the import.
Something else to deal with will be whatever custom spells and possibly items they added, assuming those are mentioned in the character entries who had them at the time and the old DBCs aren't being used now. I'm guessing that'll just be warnings from them not existing, though.
1 Guest(s)
1 Guest(s)