re: MySQL 4.03 and merge tables: bug with BETWEEN
Tac, Friday, September 27, 2002, 10:34:46 PM, you wrote: T We're having a problem with a huge merge table and BETWEEN. The same query T in MySQL 3, using an identical (binary) copy of the database, takes a T fraction of a second, in MySQL 4.03 it runs without stopping. T The query is a simple Select * from my_merge_table where my_code BETWEEN T '2026676653' AND '2026676655' T If I run a simple script that loops through the invidiual tables of the T merge table, using the same query (with each table), the response is very T fast. And running the query when the operator is '=' instead of BETWEEN, T everything is fine, e.g. T Select * from my_merge_table where my_code = '2026676653' T Expanding out the BETWEEN still causes the query to run forever: T Select * from my_merge_table where my_code = '2026676653' AND my_code T = '2026676655' I tested it on the not so big merge table (~ 150 000 rows) and it worked fine with BETWEEN. T Another bug that's in MySQL 3 (that I haven't checked in MySQL 4) is trying T to use a merge table where one of the tables has no rows. When we create a T merge table, we go through each table first and check to make sure it has T something in it, otherwise, the merge table is created ok but queries T against it return no rows. Of course MySQL will check every table to check if it contains matched rows. T Finally, does anyone know if you can now use fulltext indexes with a merge T table? We're not yet (since it's not supported), but I did see that on the T to-do list. Full-text search still works only on MyISAM tables. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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
Re: MySQl 4.03
What do you mean 'still' ? Version 4 just went beta a short time ago, and is only at 03 or 04. DonPro wrote: Hi, The web site states that MySQL 4.03 is still officially beta. Does anyone have any experience or feedback using it on a production system? I really require some of the new features in version 4. - 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 - 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
MySQL 4.03 and merge tables: bug with BETWEEN
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
