in reply to Strange experiences w/ perl 5.6.0 on linux 2.2.16-22

My suggestion would be put some checking around your sprintf, and make sure all the values you used to form your sql statement are not undef and well-formated. Most likely it is something like this. Even if not as simple as my professional guess, my suggestion would still be a good style you want take into consideration.
  • Comment on Re: Strange experiences w/ perl 5.6.0 on linux 2.2.16-22

Replies are listed 'Best First'.
Re^2: Strange experiences w/ perl 5.6.0 on linux 2.2.16-22
by diotalevi (Canon) on Dec 09, 2002 at 20:25 UTC

    And placeholders. Definately placeholders. You won't have to worry about quoting then because it happens automatically (or even for some cases it saves a step or two internally)

    my $sql = 'update upps_ret_q set state=?, message=? where seq_n=?';
my $sth = $dbh->prepare( $sql );
$sth->execute( $state, $msg, $key );

    [download]
    __SIG__
use B;
printf "You are here %08x\n", unpack "L!", unpack "P4", pack
  "L!", B::svref_2object(sub{})->OUTSIDE;

    [download]
[reply]
[d/l]
[select]
      Hmm I haven't considered parameterizing the query yet; and I will in our dev version; however, I still have a hard time swallowing that there any value I can pass to int() which will cause it to return undef.
      I guess I'll have to bump up the error checking level to try and track this down. I was hoping it was something simple since this error only decides to grace me with it's presence every couple weeks or so, yet operates fine the other 99% of the time all day.
      Tres weird.
[reply]

In Section Seekers of Perl Wisdom