Error in DB.SQL released with 0.3.9

[Xarslik]

There appears to be a problem in DB.SQL being released in the current (0.3.9) version of EQEmu. Took me a while to figure this out since I'm new to mySQL. If you examine the "CREATE TABLE account" section of the database (near the top) you'll notice the column status is being created as such, "status tinyint(5) NOT NULL default '0',". This makes a SIGNED tinyint(5), meaning it supports -128 to 127. Therefore you cannot set a user's status higher than 127. To fix this, either replace the line with "status tinyint(5) unsigned NOT NULL default '0'," OR run mySQL, use eq (or whatever your db is), and enter "ALTER TABLE account MODIFY status tinyint(5) unsigned NOT NULL default '0';". Also using the dbupdate.sql file included will fix this problem (as it uses an int, allowing a much wider range and the new ban \ suspend feature).

[DeletedUser]

unsigned doesnt allow negatives, youl put the DB totally out of wack, use the dbupdate.sql

[Xarslik]

Yeah, that's what I'm saying, by default it's using a SIGNED tinyint, which maxes out at 127, meaning you CANT set any user's status to 200. Setting it back to an unsigned int will allow it to range from 0 to 255. I'm just saying next time you release EQEmu you should either replace that line with the one in dbupdate.sql or change it to an unsigned tinyint.