We're having a problem with a huge merge table and BETWEEN. The same query
in MySQL 3, using an identical (binary) copy of the database, takes a
fraction of a second, in MySQL 4.03 it runs without stopping.
The query is a simple "Select * from my_merge_table where my_code BETWEEN
'2026676653' AND '2026676655'"
If I run a simple script that loops through the invidiual tables of the
merge table, using the same query (with each table), the response is very
fast. And running the query when the operator is '=' instead of BETWEEN,
everything is fine, e.g.
Select * from my_merge_table where my_code = '2026676653'
Expanding out the BETWEEN still causes the query to run forever:
Select * from my_merge_table where my_code >= '2026676653' AND my_code
<= '2026676655'
Another bug that's in MySQL 3 (that I haven't checked in MySQL 4) is trying
to use a merge table where one of the tables has no rows. When we create a
merge table, we go through each table first and check to make sure it has
something in it, otherwise, the merge table is created ok but queries
against it return no rows.
Finally, does anyone know if you can now use fulltext indexes with a merge
table? We're not yet (since it's not supported), but I did see that on the
to-do list.
Thanks!
Tac
---------------------------------------------------------------------
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
