Yeah, this is probably thwe right thing according to SQL.
Adding imaginary 0x00 instead of 0x20 could make it less strange, but break
compatibility...
> -----Original Message-----
> From: Kevin.Lewis@stripped [mailto:Kevin.Lewis@stripped]
> Sent: Tuesday, October 21, 2008 5:47 PM
> To: Vladislav Vaintroub
> Cc: 'Lars-Erik Bjørk'; 'Jim Starkey'; 'Ann W. Harrison';
> falcon@stripped
> Subject: Re: bug#23692 Solutions
>
> Vlad,
>
> You are right. This solution would make 0x0943 less that null. And
> you
> know what? It is, according to MyISAM!
>
> mysql> create table m1 (a char(4)) engine myisam;
> Query OK, 0 rows affected (0.01 sec)
>
> mysql> insert into m1 values (''), (0x43), (0x4300), (0x4320),
> (0x4309),
> (0x0943);
> Query OK, 6 rows affected (0.02 sec)
> Records: 6 Duplicates: 0 Warnings: 0
>
> mysql> select hex(a) from m1;
> +--------+
> | hex(a) |
> +--------+
> | |
> | 43 |
> | 4300 |
> | 43 |
> | 4309 |
> | 0943 |
> +--------+
> 6 rows in set (0.00 sec)
>
> mysql> select hex(a) from m1 order by a;
> +--------+
> | hex(a) |
> +--------+
> | 0943 |
> | |
> | 4300 |
> | 4309 |
> | 43 |
> | 43 |
> +--------+
> 6 rows in set (0.00 sec)
>
> Vladislav Vaintroub wrote:
> >> 0x 43 09
> >> 0x 43 {20}
> >> 0x 43 {[20]}
> >> 0x 43 43
> >
> > Is '\tA' ==0x 09 41 less than nothing (empty string '',expanded to
> 0x20) in
> > this convention? Is not this anomaly?
> >
> >> -----Original Message-----
> >> From: Kevin.Lewis@stripped [mailto:Kevin.Lewis@stripped]
> >> Sent: Tuesday, October 21, 2008 4:57 PM
> >> To: Lars-Erik Bjørk; Jim Starkey; Ann W. Harrison;
> >> falcon@stripped
> >> Subject: bug#23692 Solutions
> >
> >
> >
>
> --
> Falcon Storage Engine Mailing List
> For list archives: http://lists.mysql.com/falcon
> To unsubscribe: http://lists.mysql.com/falcon?unsub=1
