Bug #2821 Table default character set affects LONGBLOB fields

• Submitted: 16 Feb 2004 4:29
• Modified: 18 Mar 2004 23:38
• Reporter: Alexander Barkov
• Status: Closed
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 4.1.2-bk-current
• Assigned to: Alexander Barkov
• CPU Architecture: Any

[16 Feb 2004 4:29] Alexander Barkov

Description:
Sinisa and Victoria reported about this behaviour:

> Even if I have 2 columns in the table LONGBLOB and LONGTEXT, blob column are 
> convered to the text.
> 
> mysql> create table test1(
>     -> myblob longblob,
>     -> mytext longtext) default charset latin1 collate latin1_general_cs;
> Query OK, 0 rows affected (0.06 sec)
> 
> mysql> show create table test1\G
> *************************** 1. row ***************************
>        Table: test1
> Create Table: CREATE TABLE `test1` (
>   `myblob` longtext character set latin1 collate latin1_general_cs,
>   `mytext` longtext character set latin1 collate latin1_general_cs
> ) ENGINE=MyISAM DEFAULT CHARSET=latin1
> 1 row in set (0.00 sec)

The above is wrong, a blob field should never take the table default
character set.

How to repeat:
Run the above.

[18 Mar 2004 23:38] 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