I have a very typical problem: i am using DBI sybase: and i have a query of the form
use database go select * from table go
now i have to split the query at go and execute both the queries in the same order. the procedure which i am using is split at "go" using the split function and storing in an array. now i am accessing each element of the array and excuting it using the execute in DBI and getting the rows using fetch. but since the use database statement wont return rows its giving me eror at the fetch statment say no statment executed at that line. How do i stop it from giving me that error. I tried using if statement like
if (sth->fetch()) { code here }
but still giving me that error on the line of fetch. Please help out of this grave problem. thanks - Turumkhan

In reply to how to catch the query retunin no rows. by turumkhan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.