Re: SELECT problem after upgrading from 4.0.20 to 4.1.7

Hi!

On Feb 09, Steve Hay wrote:
> I have a problem in which a simple SELECT statement that worked fine 
> under 4.0.20 doesn't work any more after upgrading the database software 
> to 4.1.7 (but still using the database that was created by 4.0.20).  If 
> I re-create the database using 4.1.7 then the SELECT statement now works 
> again.
... 
> We need to be able to get the SELECT statements working after upgrading 
> to 4.1.7 without needing to re-create the data.  I read section 2.5.2 of 
> the MySQL 4.1.7 manual ("Upgrading from Version 4.0 to 4.1"), but could 
> not see anything relevant that I might need to do, hence I am led to 
> believe that this is bug.

It was a bug.
According to http://dev.mysql.com/doc/mysql/en/news-4-1-8.html

 The server was interpreting CHAR BINARY and VARCHAR BINARY  columns
 from 4.0 tables as having the BINARY and VARBINARY  data types. Now
 they are interpreted as CHAR and VARCHAR  columns that have the binary
 collation of the column's character set. (This is the same way that
 CHAR BINARY and VARCHAR BINARY are handled for new tables created in
 4.1.)

Regards,
Sergei

-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[email protected]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, Senior Software Developer
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
       <___/  www.mysql.com

-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]