true - thank you...but i still have the same problem
after correcting that...so i guess there are other
issues.
i think i may have found the answer though...i suspect
PostgreSQL may only support binding of literal values,
since if i leave the field name hard-coded, but bind
the string to match, it works - like so:
my $sth = $dbh->prepare( "SELECT * FROM demographics
WHERE fname LIKE ?");
$sth->bind_param(1, $text);
can anyone speak to the details of parameter binding
in DBD::Pg or postgres? there are no restrictions
listed in the docs on CPAN (other than binding output
parameters), and i can't find anything in the postgres
mailing list archives...thanks, and just ignore me if
i am getting too off-topic...
rob
--- "Sterin, Ilya" <[EMAIL PROTECTED]> wrote:
> The reason is because you already are using single
> quotes around the $text,
> when you bind it also puts quotes around it, since
> internally quote() is
> called.
>
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
