PRecompiled Binaries for Windows for use with MYSQL 5

[sesmar]

Originally Posted by Gameross

Either case, you should be working with developers to impliment this change and not doing your own thing and splintering Emu developement. Just seems to make sense.

The devs have released the newest version of the emu (0.7.0-801) to be compatable with MySql 5. However, after I downloaded the binaries and upgraded to MySql 5 (since I have been waiting for an offical release for this) I was getting client not compatable errors. Figuring this may have something to do with it the precompiled binaries having been compiled on a machine still using the MySql 4.0.x include and lib files I grabed the source and recomplied it, as it was, with the MySql 5 lib and include files. After doing this the server booted right up for me. Only problem was once I logged in and tried to cast a spell it would crash everytime.

So all I did was grab the 800 version source and made the few minor changes to the source (mostly changing the any reference to condition in sql statements to _condidtion) to make it compatable with MySql 5 as well. I recompiled the server booted it up logged in and it works great. I could not get the Zone to output debug information for some reason so I was unable to see what was causing the crashes. This is something I am working on now.

[aza77]

looks like the problem just appears at windows servers ... i tried 801 with mysql 5.0.20 and 5.0.22 and it works without problems @linux

[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;

[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.