On Thu, 2002-08-15 at 07:03, Vorce, Tim (T.) wrote:
> This is a bigger problem than I thought. I am constructing a sequence for a
> stored procedure. I'm getting in several values, and constructing the call
> to the stored procedures. I thought that oracle would support placeholders,
> but that
On Thu, 15 Aug 2002 10:03:07 -0400 "Vorce, Tim (T.)" <[EMAIL PROTECTED]> wrote:
> This is a bigger problem than I thought. I am constructing a sequence for a
> stored procedure. I'm getting in several values, and constructing the call
> to the stored procedures. I thought that oracle would sup
AIL PROTECTED]]
Sent: Thursday, August 15, 2002 9:12 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Escaping sql strings
How about...
$sql="select * from table where column=?";
$sth=$dbh->prepare($sql);
$sth->execute(qq/What you're looking for/);
Gordon Dewi
How about...
$sql="select * from table where column=?";
$sth=$dbh->prepare($sql);
$sth->execute(qq/What you're looking for/);
Gordon Dewis
Production Officer
Geography Division
Statistics Canada
(613)951-4591
-Original Message-
From: Vorce, Tim (T.) [mailto:[EMAIL PROTECTED]]
Sent: T
Tim, read the perldocs on placeholders by doing
perldoc DBI
at a command prompt, and search(with the "/" forward slash) for
"placeholder". Using placeholders has many advantages, one of
which is properly quoting data to be inserted into the database -
so that you don't have to worry about it
