Thanks for checking it out. I've just discovered an older version of the database at revision 2506 (the last SVN one) and I checked the group_leaders schema there and it's exactly what I posted above as "fix". So back then at least it was working like this for Linux and Windows alike:
2506 DB
Code:
CREATE TABLE `group_leaders` (
`gid` INT(4) NOT NULL,
`leadername` VARCHAR(64) NOT NULL,
`marknpc` VARCHAR(64) NOT NULL DEFAULT '',
`leadershipaa` TINYBLOB NULL,
`maintank` VARCHAR(64) NOT NULL DEFAULT '',
`assist` VARCHAR(64) NOT NULL DEFAULT '',
`puller` VARCHAR(64) NOT NULL DEFAULT '',
PRIMARY KEY (`gid`),
UNIQUE INDEX `U_group_leaders_1` (`leadername`)
)
It's possible that MySQL handles it differently depending on OS. I remember reading about the fact that certain problems only raise WARNINGS on MySQL for Linux while raising ERRORS on MySQL for Windows - maybe this one of those instances too.