As an aside, when using a LIKE clause, there is can be a significant performance difference between
WHERE last_name LIKE 'smith%'
and
WHERE last_name LIKE ?
The difference depends on when the database does query planning, and on how sophisticated the query planning is. A sophisticated query planner will look at the first fragment, and determine (by noting no initial wildcard) that if last_name is indexed, the index can be used to optimize the query. However, in the second fragment, the planner can't make any assumptions, and will force a linear scan of the table even if last_name is indexed. For a big table, this can clobber performance.
I know it work this way with Oracle, but haven't delved into MySQL to this depth. Perhaps someone with more experience can say whether this would also be an issue with MySQL.
| [reply]
[d/l]
[select] |
Super thanks gav^! It works. Where did you find this? I hate posting questions when they are so easily answered.
peppiv
Update:
yes tachyon, been to that site many times and learned a lot! However, it didn't answer this particular question.
I appreciate it!
| [reply] |
It's probably from how the placeholders are looked for in the query string. Since you're using MySQL, which IIRC doesn't have support for placeholders, that support is faked by the DBI level. Thus, it parses your string but doesn't look inside quoted blocks. So the placeholder in your "%?%" string isn't seen, and thus the DBI engine believes you have no placeholders, and fails on the execute.
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important
| [reply] |
| [reply] |