THIS HAS NO PRACTICAL PURPOSE
I'm at home for winter break, and I have nothing better to do, so I started adapting the server to run off of a MySQL as opposed to MSSQL.
As you would figure, this is a pretty daunting process. The good news is that the server is designed in such a way that most of the heavy lifting is done through stored procedures in the database. This means that we shouldn't have to make too many changes to the server source code to make this work... right? The bad news is that the servers don't make use of ODBC properly, so I'm going to have to go in the source and change the calls anyway. Sucks right? Yeah... Well, at least after we've made the changes to the source, you'll be able to use the same source code with any other database you can find an odbc adapter for.
Anyway, I'll be updating this post as I make progress, and I'll try to make comments explaining what I can figure out about the database. Feel free to correct any mistakes I make.
You can test these by creating MySQL DSNs in odbcad32.exe, and naming them properly. You'll have to go into the source code and change references to the stored procedures as well to make it work. Here's an example:
Code:
// /ACCOUNTSERVER/DBManager.cpp
sprintf( qryAccount, "LOGINJOIN_STR '%s', '%s'", Gu, szAccount );
[SIZE=5][SIZE=2]
// Should be changed to...
[/SIZE][/SIZE][SIZE=5][SIZE=2]
[/SIZE][/SIZE]sprintf( qryAccount, "{CALL LOGINJOIN_STR ('%s', '%s)}'", Gu, szAccount );Green = Mostly Usable
Orange = Partially Usable
Red = Not Usable
Last edited: