Bug #2244 User variables collation conflict is not detected

• Submitted: 31 Dec 2003 5:49
• Modified: 31 Dec 2003 11:30
• Reporter: Alexander Barkov
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.1.x
• OS: FreeBSD (freebsd)
• Assigned to: Alexander Barkov
• CPU Architecture: Any

[31 Dec 2003 5:49] Alexander Barkov

Description:
select @a:='test' collate latin1_general_ci,@b:='TEST' collate latin1_bin, @a=@b;
+--------------------------------------+-------------------------------+-------+
| @a:='test' collate latin1_general_ci | @b:='TEST' collate latin1_bin | @a=@b |
+--------------------------------------+-------------------------------+-------+
| test                                 | TEST                          |     1 |
+--------------------------------------+-------------------------------+-------+

The above should produce collation conflict error.

How to repeat:
run the above

[31 Dec 2003 5:53] Alexander Barkov

This query does not produce error too:

select @a:=('test' collate latin2_general_ci),@b:=('TEST' collate latin2_bin), @a=@b;

[31 Dec 2003 7:07] Alexander Barkov

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html