There's nothing magic in the undef
you have to pass to the do
method. The required interface when you want to pass bind variables is the following:
$dbh->do($statement, \%attr, @bind_values);
is the query string. \%attr
indicates a reference to a hash where you can pass additional attributes (much like the ones you pass to the connect
method). Then, you can put a list of values to bind to the various '?' you put into $statement
is an array, but it's been put only to indicate that more values are expected here).
If you don't want to pass additional attributes, you simply put an undef where \%attr is expected. So you end up with something like:
$dbh->do($statement, undef, @bind_values);
It's really nothing more than this.
Regarding the matter of grabbing the counter value, this is plain wrong, both syntactically (you close a paren that you never open) and semantically (assigning that list to the $counter variable isn't going to help you get the counter from the DB, is it?):
my $counter = 'SELECT pagecounter FROM counters WHERE pagename = ?'
On the other hand, this is incomplete:
my $sth = $db->prepare('SELECT pagecounter FROM counters WHERE pagenam
+e = ?');
because you still need to get the result and put it inside some variable (e.g. with fetch_whatever
). My solution merges it all into a single call, and gives you the counter's value directly inside the $counter
my ($counter) = $db->selectrow_array(
'SELECT pagecounter FROM counters WHERE pagename = ?',
functions gives you the first row of the result as an array, and we know that at most one record will be given for this query. Moreover, we already know that this array is going to contain one item only (because I'm SELECTing only the pagecounter field), so assigning this array to the list ($counter)
simply puts the desired page counter into the $counter
Hey! Up to Dec 16, 2007 I was named frodo72, take note of the change! Flavio
Io ho capito... ma tu che hai detto?
perl -ple'$_=reverse' <<<ti.xittelop@oivalf