Arias Gonzalez, Javier wrote:
Assuming we have the following table:
CREATE TABLE test (
id INT NOT NULL,
last_name CHAR(30) NOT NULL,
first_name CHAR(30) NOT NULL,
PRIMARY KEY (id),
);
With last_name having 1,000 different values and first_name having
1000,
Assuming we have the following table:
CREATE TABLE test (
id INT NOT NULL,
last_name CHAR(30) NOT NULL,
first_name CHAR(30) NOT NULL,
PRIMARY KEY (id),
);
With last_name having 1,000 different values and first_name having
1000,000 different values... What is be
In the last episode (Jun 01), [EMAIL PROTECTED] said:
> i have one multiple column fulltext index for 3 columns i join in a
> fulltext match statement
Fulltext indexes are different from regular indexes. I don't think it
matters what order the columns are in.
--
Dan Nelson
[EMAI
i have one multiple column fulltext index for 3 columns i join in a
fulltext match statement
> In the last episode (Jun 01), Daniel Rossi said:
>> hi just reading up on optimising indexes, does it matter what order u
>> set your indexes ?
>>
>> The first index part should be the most used column.
In the last episode (Jun 01), Daniel Rossi said:
> hi just reading up on optimising indexes, does it matter what order u
> set your indexes ?
>
> The first index part should be the most used column. If you are
> always using many columns, you should use the column with more
> duplicates first to g
hi just reading up on optimising indexes, does it matter what order u set your indexes
?
The first index part should be the most used column. If you are always using many
columns, you should use the column with more duplicates first to get better
compression of the index.
i dont really under
