Issues with MySQL

[Crosier]

This is my first attempt at setting up a EO private server.

At first I was considering using the Mannequin Database/Server/Client, but I've decided to go with .

I've followed most instructions as written in by Drenferalis. I have, however, deviated where it comes to MySQL. I am not using winmysqladmin, Wamp, or XAMPP. I have instead opted to use a standalone installation of and the .

As a part of the troubleshooting process, I've tried viewing all the tables of the Rainbow Database one-by-one. Most of the tables opened without a fuss, but about a tenth or so of the tables gave the following error:

Error Code: 1034. Incorrect key file for table '[I]Table name here[/I]'; try to repair it.

Here is a list of the tables affected:

 Spoiler

account
account_c
account_old
account_pwd
ball_card
columns_priv
cq_card
cq_card2
cq_card3
cq_leaveword
cq_sys_leaveword
cq_user
cq_userbroken

I redownload the database and inspected it again, but the exact same set of tables were affected.

Any idea how to get this database working with MySQL Community Server 5.5.27? Any ideas what could be causing this incompatability?

 Spoiler

I got part way through setting up Mannequin before I decided to switch to Rainbow DB. During that time, I did try to inspect the Mannequin database, and if I recall correctly, its 'account' table gave the same error as the Rainbow DB tables. Unfortunately, that was the only table in Mannequin's database that I examined, but I am fairly confident that I would have found it had problems nearly identical to Rainbow DB's had I inspected all of them.

i.e., I don't think it's a problem with the specific release.

If needed, I can reload the Mannequin database and inspect the tables to confirm this.

Aside from that, I'd also like to know what differences there are between a straight installation of MySQL and the MySQL installed with winmysqladmin that might have an effect on the EO Server programs.

(I am using the 64-bit versions of Windows 7 and MySQL CS 5.5.27, if that makes any difference)

[Timore[PM]]

Lol EO doesn't support mysql 5.0+

[Crosier]

Really? That surprises me a bit. I was under the impression that something like SQL (or MySQL) would be designed and updated with some backwards compatability in mind.

So just what version of MySQL was EO built around, exactly? (Not necessarily the version that is typically used, but the version whereabouts that was used for the EO Server when it was first released)

In the meantime I think I'll take a look at what functionality MySQL dropped/changed in version 5.0 to create this incompatability, just for fun and curiosity's sake.

 Spoiler

...In retrospect, I suppose I should have given more thought to just how antiquated WinMySQLadmin is:



Ver 1.4 for Win95/Win98/NT/Win2000? That goes pretty far back.

Oh well, I'd still like to try cramming this round peg into this square hole for a while longer... because I'm just stubborn like that.

[Timore[PM]]

Originally Posted by Crosier

Really? That surprises me a bit. I was under the impression that something like SQL (or MySQL) would be designed and updated with some backwards compatability in mind.

So just what version of MySQL was EO built around, exactly? (Not necessarily the version that is typically used, but the version whereabouts that was used for the EO Server when it was first released)

In the meantime I think I'll take a look at what functionality MySQL dropped/changed in version 5.0 to create this incompatability, just for fun and curiosity's sake.

 Spoiler

...In retrospect, I suppose I should have given more thought to just how antiquated WinMySQLadmin is:



Ver 1.4 for Win95/Win98/NT/Win2000? That goes pretty far back.

Oh well, I'd still like to try cramming this round peg into this square hole for a while longer... because I'm just stubborn like that.

Its possible to use the new ones, but there are quite a few changes in it. I'm taking up the challenge of doing so because i heard hio was able to do it.

[PowerChaos]

eo and those games use mysql version 4.0.12
use version 5.x and you create a lot of bugs

mysql is designed to be backward compitable on certain things , just like php and apache
some bugs are fixed in them and to fix a bug means that some commands are rewritten

also the version 5 does have more functions in it then the version 4 , that makes it that the 5 is missing stuff that the version 4 does not need

more info about mysql versions can be found at following link


smal quote that solves your problem

Important Change: If you upgrade to MySQL 4.1.1 or higher, it is difficult to downgrade back to 4.0 or 4.1.0. That is because, for earlier versions, InnoDB is not aware of multiple tablespaces.

and probaly it just need that part to work good

Greetings From PowerChaos

[idlemonkey]

.

[PowerChaos]

Originally Posted by idlemonkey

open your script and actually type the tablename where it says 'Table name here'

Lmao roflol

This is the best answer I reader for now

Showing a quote and providing a solution for that quote

Lucky that he understand that it goes about MySQL 5.5

Greetings from powerchaos

[funhacker]

As for your error you were getting, that's because you've put mysql4.0 tables into a mysql 5.5 database, you'd need to migrate them by dumping or running a program that will do this safely.
However after 4.0 "TYPE" was changed to "ENGINE" and things like timestamps no longer have a length property.