On Tue, Nov 19, 2002 at 07:12:27AM +1100, Dean Harding wrote: > Actually, it's a slightly different problem - a very uneven distribution > of values on a column, not a small number of possible values like a > bitmap index is for.
Exactly. > In my opinion, this is a pretty useless feature, I mean the whole > *point* of the optimizer is to see things like that and do a full table > scan when it's going to be faster. Well... > I guess I can see the point if the row is only *added* to the index if > it matches the WHERE clause. That'd speed up the index management as > well. Bingo. That's it. Speed up, save space, save CPU, etc. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 104 days, processed 2,262,358,069 queries (250/sec. avg) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
