This is really not that urgent or needed atm. The database works pretty good as is. In my case, I just had a bad idea (classify the loot tables into too large numbers), and was able to fix it. With a lot of thought, it probably could be done properly.
After a lot of work with the databases, you start to "get the big picture" on how it all works, and what needs what. I use a lot of tools when I do db work, but the one i most use and recommend is the "mysql-query-browser", for its simplicity and usefulness. mysql-query-browser is one for you to start with, and will always find use, even when you become advanced.
The database needs to be cleaned up and organized mainly so you don't have to be a "MySql Guru" in order to find/change things. It will be hard to do this, as first thing that would need fixing are things like the in-game #spawn commands (they don't look at the zone you're in, they only look at what the last number was) and editors (PEQ Editor). Even if we did organize the database, next person that #spawns something or uses an editor for adding loot, will have it all out of place again.
When I work with spawns and drops, I'm now aware of what happens, so I at least try not to make things worse. In Hollowshade, I cleaned it up, organized it before I started (as best I could). If you do look at that zone, it will be easier to make some sense out of it all.
Then, there's something else: What to do with your fixes and how to make them useful to everyone? Because if you do it just for yourself, it will soon become forgotten. There are three "public" database; EQ, AX_CLASSIC, and PEQ. EQ is the original database that Cavedude made public for all of us to use, Cavedude has since turned to PEQ and is supporting their database, so making/posting a SQL for EQ DB is a bad idea, since he is not building on it anymore. AX_CLASSIC is my DB , which I originally started (AX_PEQ) and stubbornly maintained mostly by myself, because at the time (lately, I just don't know how to give it up), no one was doing anything, and I wanted to do something. I'm "running out of steam", and am looking at ways to port my stuff over to the PEQ database. Already have ported all my LoY work, Hollowshade, and more. PEQ is the way to go, everyone that wants to do "public" work, goes there - and there is no need for any "forks" of any kind. At PEQ. there actually is a working team which is more than anyone has ever done in the database area. So, if you do manage to make some changes, do it under PEQ and run it by Cavedude, he will work it in. The way to do this, is to have a SQL available for him to look at, test, and finally source in. You can post the SQL here, we can verify it for you.
|