| Subject: | Select failure on indexed tables |
| Date: | Tue, 24 Mar 2009 10:28:12 +0000 |
| To: | bug-DBD-mysqlPP [...] rt.cpan.org |
| From: | Chris Dent <chris [...] cjvdent.com> |
In a utf-8 table with utf_general_ci collation, queries designed to
identify existing database entries such as
SELECT `ID` from `Addr` WHERE ((`Postcode`='AB23 0UL') AND
(`Address`='23 Royston Grds, Stirling'));
were working perfectly until I indexed the (myisam) tables. Statement
handles now prepare but will not execute: perl just hangs. Dropping the
(btree) index means they work OK again. Of course, they execute
perfectly on indexed utf8 tables from the MySql command line.
I thought this might be related to the last utf8 bug report but
converting the tables to latin1 (ALTER TABLE `Addr` CONVERT TO CHARACTER
SET latin1;) and the queries still will not run successfully on indexed
tables.
It's not just text indexes that throw a spanner in the works either.
Indexing a table on one or two timestamp fields also results in the same
error independent of the charset.
FWIW, MySQL 5.1 on XP SP3, latest mysqlpp.
Hope you can fix this quickly as my app is creaking!
Chris