I have a MyISAM merge table that works with MySQL 5.0.27, but fails when =
I try
to upgrade to 5.0.37. The error is 1168: "Unable to open underlying =
table which
is differently defined or non-MyISAM type, or doesn't exist."

The problem is, they *do* exists. When I switch back to 5.0.27 =
everything works
fine. Can anyone tell me what changed that is failing these?

I can't tell exactly which version change broke this, as I missed the =
updates
between ,27 and .37, and old binaries are not available for DL on =
MySQL.COM.
I'm running MySQL on Windows 2003 Server, with 2Gb RAM.

I guess my next step will be to switch to .37 temporarily, and print out =
table
structures for all the tables & the merge. Maybe I can spot some =
difference
among them (like MyISAM version) that .27 didn't care about.




--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32 [at] m.gmane.org

Guy Gordon wrote:
> I have a MyISAM merge table that works with MySQL 5.0.27, but fails when I try
> to upgrade to 5.0.37. The error is 1168: "Unable to open underlying table which
> is differently defined or non-MyISAM type, or doesn't exist."
>
> The problem is, they *do* exists. When I switch back to 5.0.27 everything works
> fine. Can anyone tell me what changed that is failing these?

It sounds like you may be hitting http://bugs.mysql.com/bug.php?id=26881. This bug doesn't affect 5.0.27.

Best regards,

--
Todd Farmer, Support Engineer
MySQL Inc., www.mysql.com

MySQL Conference & Expo - http://www.mysqlconf.com/
April 23-26 in Santa Clara, California (US)

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32 [at] m.gmane.org