I'm using version 4.1.1-alpha, running on RedHat Linux 9.
Victoria Reznichenko wrote:
Matt Mastrangelo [EMAIL PROTECTED] wrote:
How can an InnoDB table be created with case sensitive collation? The
example below creates two identical tables, one MyISAM and the other
InnoDB. The InnoDB fails
I'm running version 4.1.1-alpha. The 3 select statements below on the
following test table produce inconsitent results:
create table test (test varchar(20)) charset latin1 collate
latin1_general_cs;
insert into test values ('abcField1');
insert into test values ('abcField2');
insert into test
How can an InnoDB table be created with case sensitive collation? The
example below creates two identical tables, one MyISAM and the other
InnoDB. The InnoDB fails when inserting primary keys that differ in case
only. What am I doing wrong?
Thanks.
drop database test;
create database test
***
Table: test
Create Table: CREATE TABLE `test` (
`myblob` longtext character set latin1 collate latin1_general_cs
) ENGINE=MyISAM DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
Thanks.
Victoria Reznichenko wrote:
Matt Mastrangelo [EMAIL PROTECTED] wrote:
I'm using mySQL 4.1.1a-alpha on XP
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
