comment on

Your best bet for now is to disable the test in these cases. The original test was (very) wrong and the new test is incomplete and thus broken for now. The new code could look something like:

   my @req_prm = $stmt->params ();
   unless (@req_prm == 1 && ref $req_prm[0] eq "SQL::Statement::Param"
+) {
       my $n_req = @req_prm == 1 && ref $req_prm[0] ? $req_prm[0]->num
+ : scalar @req_prm;
       unless ($n_req == (my $nparm = @$params)) {
           my $msg = "You passed $nparm parameters where $n_req requir
+ed";
           $sth->set_err ($DBI::stderr, $msg);
           return;
           }
       }
[download]

But do not see this as a fix, as it is cowardly running away from problems hiding in the dark.

Enjoy, Have FUN! H.Merijn

In reply to Re^5: "You passed 0 parameters where 1 required" error using DBD::CSV, an INNER JOIN, and a WHERE clause by Tux
in thread "You passed 0 parameters where 1 required" error using DBD::CSV, an INNER JOIN, and a WHERE clause by planetscape

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks