PRecompiled Binaries for Windows for use with MYSQL 5

[Coleshadowblades]

I fail to see how it can be a windows specific error to be honest... Seems alot of the bugs in the code get pawned off as a windows error simply cause noone wants to just plain fix them all around.

See here are a few issues ive noticed...

Dirty code

all the devs aint on the same page with the style of coding to be employed thereby all doing their own thing and this shows in the code

instead of coding to work on both types of syste (windows and linux) The devs seem to only wish to develop based on linux.

Now when ya got people like sesmar (And im learning pretty quick thanks to him) Who do stuff for windows instead of a thank you for getting it working we get accused of splintering the project... Got news for you i prefer linux however im smart enough to know itll NEVER be as used nor popular as windows

[gottasummer]

I can see how it is a precompiled binary specific error.

The MySQL includes and libraries that are in this build must (well, I don't know about must... but SHOULD) be the same as those that are in use on that system.

If I build EQEmu with MySQL version X.XX, the machine I put it on should also run MySQL version X.XX

[Coleshadowblades]

I said WINDOWS specific meaning everyone says "oh thats a windows only error" instead of actually fixing it they pawn it off on windows and just leave it be lol

[Coleshadowblades]

this post is precisly why people dont share their fixes and such with the community... I am removing the binaries can a mod please delete the posts reguarding getting it to work with mysql 5 made by me please?

EDIT the binaries are no longer available for download

[WildcardX]

I was gonna post the following SQL changes needed for MySQL 5 support, but I see two of the SQL lines are already posted here... Anyway, you need to do the following SQL:

alter table account change packencrypt packencrypt blob NULL;
alter table character_ change extprofile extprofile blob NULL;
alter table player_corpses change data data blob NULL;
alter table player_corpses_backup change data data blob NULL;

[WildcardX]

Also note... One reason why the unix/linux peeps may be saying "looks like it's a problem on Windows servers" is probably because when they loaded MySQL 5 or already had it loaded, it probably doesn't run in strict mode, but strict mode is on by default for a windows installation. Strict mode ensures you are using only proper MySQL 5 commands. On linux and unix installations or any other platform with this turned off, MySQL 5 allows you to "fudge" your commands. It's a bad habbit really and strict mode really should be turned on, in my opinion.

[fireclav]

just to clarify, which binaries do i dl (using windows). saw a few in here and didnt wana dl the wrong thing and get my server all messed up

[johane]

Originally Posted by Coleshadowblades

I said WINDOWS specific meaning everyone says "oh thats a windows only error" instead of actually fixing it they pawn it off on windows and just leave it be lol

I don't recall the exact fix, but this is probably due to the changes in how case is handled in table and field names that happen in MySQL 5. The Windows bit is due to Windows being ^&%*&%* about case handling in general.

There's a setting you can use in my.conf to use "old style" case handling for Windows machines. Look it up.

There's also new string handling functions that should be used, but I can't recall exactly what they are. Most people I know just don't let Windows try to be a server that runs MySQL....

Note that this is not intended to be a flame of any kind. But that's probably why you've got the error.

The flame war stops now, I dont care who you are or what you have done.

Stop now, you want to flame take it to PM's.