Alex,
sorry, but it is not a planned enhancement for a long time. For small
columns it is as good to create an index on the whole column, because
there is at least some 15-byte space overhead for secondary index records
anyway. For large columns the application can add an extra column to the
tabl
Heikki,
Could you please tell me (and add in the manual perhaps) if this is
a planned enhancement or not and if it's planned, if it will be
added in a long or a short delay.
Thanks,
Alex.
HT> Innobase does not support partial-field indexes. We have to block their
HT> usage in th
Hi!
Innobase does not support partial-field indexes. We have to block their
usage in the SQL parser. Miguel's query on Win NT perhaps worked because the
optimizer there chose another access path and did not use the partial-field
index.
But thank you Alex, we have to block them in the parser, and
Bonjour,
Sorry I mistyped the version of Mysql with which we have the bug.
It's Mysql-3.23.36 with patch correcting Solaris and other non Linux
Unix problem.
> We found a bug in INNOBASE tables with col_name(length) indexes.
>
> Here is the table :
>
> create table test (
> symbo
At 12:30 12/04/2001 +0200, BAUMEISTER Alexandre wrote:
Hi,
Maybe this issue is relative at your compiled version or platform
because I wasn't be able to repeat:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
c:\mysql\bin>mysql test
Welcome to the MySQL monitor
Bonjour,
We found a bug in INNOBASE tables with col_name(length) indexes.
Here is the table :
create table test (
symbole char(20) not null primary key,
libelle char(100) not null,
index id_lib (libelle(1))
) TYPE=INNOBASE;
For the test I insert one row but there can be many, th
