Hi ravi45722,
Yes, this is a not very informative message from MySQL. You can help by placing
DBI->trace(2);
in your script; this will print out a lot of information including the actual SQL passed to MySQL, which will probably help you spot your problem. See
DBI TRACING.
Your error is probably not caused by the string value in $system_id: your use of placeholders makes quoting the values you are going to pass to the DBI unnecessary.
Also note that since you are passing the RaiseError attribute you don't need the or die $DBI::errstr after your calls to your DBI methods.
Hope this helps!
The way forward always starts with a minimal test.
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.