To test the char vs byte index I created a unique bcol(2), on a tiny text
utf8 field.
I then preceded to insert the numbers 00..99 in Chinese whose hex values
are below. Since we are using utf8 vs ucs2 they are going to be 3 bytes
per char, totaling 6 bytes per numbers.
If the index is ind
On Sun, 4 Sep 2005, Alexey Polyakov wrote:
Why do you choose to convert varchar to tinytext? Doesn't look like
good idea to me.
trailing spaces and mysql 4.x
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
Bytes IIRC. Depending on actual content it can be 127-255 characters.
Why do you choose to convert varchar to tinytext? Doesn't look like
good idea to me.
--
Alexey Polyakov
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[E
if I switch name to TINYTEXT and index 'name' to (name(255),ppathref),
will it handle utf8? that is the prefix of 255 chars or 255 bytes?
CREATE TABLE paths (
id int(11) NOT NULL auto_increment,
typeref tinyint(4) NOT NULL default '1',
name varchar(255) NOT NULL default '',
ppathref i
