would be used instead even though
the fulltext-index would have been better. But that's not so bad - we would
scan maximum 999 rows with the use of another index - no problem! ...not
compared to my 100.000 rows scans that's the result of picking a
fulltext-index when it gives a lo
Hello!
I never got any comment on this one...
Have noone else observed this behavior?
I'm a bit worried to use this in my production site without knowing if it's
and indication of some problem with FULLTEXT indexes... :)
Regards,
Tobias Lind
Hi!
I have a question regarding "C
I'm running MySQL 4.0.10, rpm-binary version.
Red Hat Linux 8.0
Dual P3400 MHz, 768 Mb RAM.
On other tables (with less number on indexes), I have always got a
cardinality after running "analyze table" also on fulltext-indexes.
Could this be a bug? Something to worry about?
Regar
Thanks - that would be great!
I'm sure a lot of people will find this very helpful.
Regards,
Tobias
- Original Message -
From: "Michael Widenius" <[EMAIL PROTECTED]>
To: "Tobias Lind - Telia Internet" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]
Hi!
I'm in the same position as Steve: Considering switching from MyISAM to InnoDB because
of the
row-level locking capabilities. My application has quite a lot of updates/inserts
mixed with
selects, and is starting to suffer from the table-locking policy...
And like Steve, I'm also scared! :)
I
ainboard you are using for the Athlons, and what
Linux-kernel
version you're running...
Thanks in advance!
/Tobias Lind
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mys
