I think that seeing more of the actual code would be helpful. The question is, why is your DBD::CSV::Statement object not a valid SQL::Statement object?
It may be that $query contains some metacharacter that is causing problems. Using either $dbh->quote() or placeholders will avoid this problem:
my $sql = "select title from $TABLE2 where astype like " . $dbh->quote("%$query");
I generally prefer using placeholders:
my $sql = "select title from $TABLE2 where astype like ?";
my $sth = $dbh->prepare($sql) or die "Cannot prepare: " . $dbh->errstr
+();
$sth->execute("%$query") or die "Cannot execute: " . $sth->errstr();
Note that, if you use a placeholder, the placeholder must substitute for the entire string being matched, including any wildcards.
P.S. $ and @ interpolate in double-quoted strings, but % does not.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.