Hi Monks,
I'm befuddled because I Perl DBI program that's been running for over a year has suddenly started complaining about a prepared statement. I have a feeling that my system admin must have updated something, but this really shouldn't be something that breaks. I was hoping someone here has seen it and might be able to shed some light into why it happened suddenly. Here's the code (just the important parts):
my $sh = $dbh->prepare("select * from records where date <= ? order by
+ date asc, time asc limit ?,10000")
|| die "Could not prepare select: " . $dbh->errstr;
my $date = "2005-02-26";
my $n = 0;
$sh->execute($date, $n)
|| die "Could not execute select: " . $dbh->errstr;
This code dies because the $n value seems to be interpreted as a string, so the prepared statement ends up quoting it in the limit portion like so " limit '0',10000", which MySQL doesn't like.
Again this was working fine a few days ago and broke abruptly, I'm assuming, because something was updated. Has anybody seen this and better yet, knows of a work around?
Thanks much,