I agree it should have bitched to high heaven when the SQL didn't parse correctly. In the past I have found that SQL::Statment is not very mature and you need to keep it up to date. Old versions are VERY buggy.
For what it's worth: I always build my SQL in a scalar before sending it to prepare(). Then I can print it out while debugging to make sure what you built is what you expected. Typically I code against Postgres and will simply copy and paste the "debug" statement into the DB's shell to make sure it does what I think, a luxury you don't have with DBD::CSV.
My code often looks like this when I am debugging it:
my $sql = "create table x as (y text)";
#DEBUG (it's this output that I copy/paste)
print "$sql\n";
#or perhaps die "$sql\n";
$dbh->do($sql) or die $dbh->errstr()
...
If your only inserting data to a CSV file (as opposed to doing selects, etc) you might consider just using Text::CSV_XS which eliminates a lot of complexity/overhead.
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.