Matt Mastrangelo <[EMAIL PROTECTED]> wrote:
> I'm using mySQL 4.1.1a-alpha on XP Professional.  When I execute a 
> create table script containing a COLLATE clause, all LONGBLOB fields are 
> silently changed to LONGTEXT in the resulting table.  This behavior does 
> not occur on version 4.1.0-alpha. 
> 
> Is this field type change intentional?  It can be circumvented by 
> setting a default collation at the database level, in the CREATE 
> DATABASE statement.
> 

Could you provide CREATE TABLE statement?
I wasn't able to repeat it:

mysql> create table test(
    -> myblob longblob) collate latin1_german2_ci;
Query OK, 0 rows affected (0.08 sec)

mysql> show create table test\G
*************************** 1. row ***************************
       Table: test
Create Table: CREATE TABLE `test` (
  `myblob` longblob
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_german2_ci
1 row in set (0.00 sec)



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
       <___/   www.mysql.com





-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to