PRecompiled Binaries for Windows for use with MYSQL 5

[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

[Coleshadowblades]

I removed the binaries from My server I will replace them shortly thanks Wildcardx for the other mysql alterations I havent found those bugs yet. Yes you are quite correct about why they are so quick to point out its a windows only problem , linux mysql is mysql 5 in non strict mode which allows for dirtier lazier coding of the mysql commands, such as not making fields that have no value untill something happens null. for instance. Now here is the other problem the devs haventupdated the solution files or anything for compilation on windows in quite some time there are files that are missing and not used anymore that are left in the proects and so forth. What the devs ar eneglecting to understand is the main userbase uses WINDOWS MOST people do. and if they are going to offer windows binaries they need to dev for windows compatability as well...

[fathernitwit]

The official automatic builds will still only support mysql 4.0 because the mysql runtime libraries are not binary compatible, and as such a binary built against the mysql 4.0 libraries will not work with a mysql 5.0 (or even 4.1 it seems) runtime... however I believe that you COULD install the 4.0 client libraries and the 5.0 server, get eqemu to use the 4.0 client, and connect to the 5.0 server (just a guess)... so far, I havent seen any concrete evidence that 4.1 or 5.0 is any better for eqemu, so until that happens (or 4.0 becomes too hard to obtain), the auto builds will stay on 4.0.

As for the "it is a windows thing" statements, the fact of that matter is that Doodman and I use linux for our servers and development, and as such, do not test the code on windows. Occasionally, I spend some time to build on windows and do basic sanity tests, but I am neither set up nor willing to do extensive testing on windows. We welcome any contributions made by the community to improve windows compatibility.

Please do not take such a negative attitude in the future towards the work we do here. Talking crap about us or the code does nothing but aggrivate us, help is appriciated, criticism without solution provided is not.

[WildcardX]

Please don't get me wrong FNW, I am not critizing you or doodman. I am just pointing out a fact that the installation of MySQL 5 for a Windows platform has strict mode turned on and that I believe it is just the opposite for other platforms such as linux, and thus, that is why some people see this particular problem has a "windows" problem. Personally, I could care less what people use to develop with. They are all tools, in my view.

Anyway, I'm not critizing you or doodman or anyone else. All I am saying is the installation is different depending on your platform and that, in my opinion, I favor the use of strict mode in MySQL 5 to enforce proper MySQL 5 command syntax. Again, just my opinion and your milage may vary.

[WildcardX]

As for the which version of MySQL to support dilema, right now it doesn't take much to get the emulator to use MySQL 4.1 or MySQL 5.0. For MySQL 5.0, the only real code change needed was to change the queries that referenced that "condition" column to "_condition" instead. Other than that, it was just a matter of not setting text or blob types to any Default values in the database script and then all you have to do is to compile while referencing the correct MySQL libs.

I agree for now the official builds should go on to support MySQL 4.0.26. But as coding goes forth, I know I'll continue to use MySQL 5.0 now so if/when I see any other code that is too 4.0.26 specific to function on 4.1 or 5.0, I'll not it and I hope you or doodman will use that code so the codebase itself can be used for any MySQL version as long as the server operator does the compiling themselves.

[fathernitwit]

my comments above were not directed at you.

Further, yes, the goal is to keep the code base mysql-agnostic for people compiling their own version, so please continue to help us keep up with the newer versions (since we will not likely be using them ourselves) as long as the changes continue to be backwards compatible.