in reply to Re: DBI (incorrectly) bound variables
in thread DBI (incorrectly) bound variables

Well, the variable being bound incorrectly is the second ($start_item) not the first ($self->param('catalog_id')). However, the ideas hold true. I did try:

$sth -> execute( $self -> param('catalog_id'), 0 + $start_item, 20 );

without success. Also $start_item + 0 and int($start_item). I just tried the specific type binding you recommended, and that did work:

$sth->bind_param(1, $self->param('catalog_id'), SQL_INTEGER); $sth->bind_param(2, $start_item, SQL_INTEGER); $sth->bind_param(3, 20, SQL_INTEGER); $sth->execute();

This leads me to believe I am experiencing a bug in DBI. (My database is MySQL.) However, this still begs the question, how is DBI evaluating the result of int($start_item) differently than the $this_stupid_counter above?

Replies are listed 'Best First'.
Re^3: DBI (incorrectly) bound variables
by diotalevi (Canon) on Jan 31, 2003 at 22:05 UTC
      Great stuff, thanks. I do intend to look into this in more detail in a week or two, unfortunately I'm a little under the gun to get this done right now, and the specific parameter binding works fine until then.
Re^3: DBI (incorrectly) bound variables
by diotalevi (Canon) on Jan 31, 2003 at 20:55 UTC

    I've seen this discussed regarding MySQL. It's just not tolerant of perl's data typing the way other databases are. If you want a better test then involve Devel::Peek and Dump() the values. Let me know what output you come up with, I can imagine I'll eventually have the misfortune of using MySQL as well and it'll be useful for to know then. My sympathies.

    Seeking Green geeks in Minnesota