This is a slightly thorny problem—when I was working on some tests with DBD::Mock, I tried to come up with a good general solution for this issue and the possibility of failure during a prepare call, and ran out of time to do it. I did come up with an adequate hack for this part, though: 

@@ -1081,7 +1087,11 @@
 #    print STDERR "Adding Results: " . (join " | " => map { join ", "
+ => @{$_} } @{$current_state->{results}}) . "\n";
     # copy the result sets so that 
     # we can re-use the session 
-    $dbh->STORE('mock_add_resultset' => [ @{$current_state->{results}
+} ]);
+    if (my @results =  @{$current_state->{results}}  ) {
+        $dbh->STORE('mock_add_resultset' => [ @results ]);
+    } else {
+          $self->{state_index}++;
+    }
 }
 
 sub verify_bound_params {

[download]

To use it, you'd put an entry in the session looking like {statement => "select ...", results => [] } at the place you expected the prepare to happen, then normal entries for the execute calls.

Hope this helps!


If God had meant us to fly, he would *never* have given us the railroads.
    --Michael Flanders

In reply to Re: How to mock results to repeated $sth->execute() calls (DBD::Mock::Session) by ChemBoy
in thread How to mock results to repeated $sth->execute() calls (DBD::Mock::Session) by tirwhan

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.