I think the better solution is that next time the database be kept internally until the next emulator release, in which a new db.sql is supplied.
Drawde did this as a favor to get people up and running with the new faction templates. A little work on the part of the users might be required, especially since he was basing the database off CVS code that I sent him.
The updated CVS db.sql is updated frequently on sourceforges CVS, its just a matter of walking over there and downloading it, I personally dont feel Drawde needs to be responsible for testing his database against everyone elses goofy db design. He specificlly stated it had an updated trade skill struct.
I don't understand what can be wrong with his db.sql, it just sounds to me like you didnt know what to do with it. The db.sql does not go over the top of an existing database. If you didnt create a new database, and tried to lay in the new db.sql over the old one, no wonder you got a ton of errors. Thats a user error, not a problem in anything Drawde did. If you had dropped your original database, created a new one, source in the new db.sql, then applied the addon, you would have gotten nothing more than a couple of bugs in a couple of sql files (mostly dupe errors), which will be ignore with a mysql -f insert.
Just my 2 cents.
__________________
Quitters never win, and winners never quit, but those who never win and never quit are idiots.
|
Threaded Mode
