PEQDB inquiry.

[vales]

Originally Posted by cavedude

Hundreds sometimes even thousands of database changes go in daily by several of us, at a mysql prompt, through the PHP editor, and even in-game. While everything is logged, it would not be feasible for me to round them all up and put them into update files. I'm lazy about the current system as is which I've made largely automatic.

Separating the tables isn't a great idea, because as GeorgeS said many tables inter-connect making it real easy to make a mess of the DB if an update gets fudged.

I like the single file mainly because it is as fool proof as one can get with DB sourcing. You don't have to worry about missed or outdated updates, conflicting data, etc. People manage to mess up the current system as is, I couldn't imagine the support requests I'd get if I separate the files or offer individual content updates.

Ah, okay then. Sounds fair enough.

[GeorgeS]

Ok I thought this out some more, and it's doable with the current schema IF you do the following. You create a flag field in NPC_TYPES called "CUSTOM" and whenever you make a custom change in the table, the flag becomes = TRUE, you can export that NPC and all dependant tables with either a perl script or .net code. It's pretty clear to me how it should work, and I'm pretty sure it will. IF you want something like this, I can code a backup and restore script.

When you load a new PEQ db from scratch, you can restore by running the script you made earlier, restoring your custom npc's. This can even be applied to items as well.

GeorgeS

[vales]

That would be most awesome if you could do that, George.