On 6 Jun 2001, at 14:44, SAWMaster wrote:
> So now I'm playing with this line...I think it's where my error is.
> $sqlstatement = "INSERT INTO Full (freq, loc, desc, freqtype, cat,
call,
> tx) VALUES ($newfreq, $newloc, $newdesc, $newfreqtype, $newcat,
$newcall,
> $newtx)";
> Can someone set me
On Wed, 6 Jun 2001, Curtis Poe wrote:
> Might I suggest that you use placeholders? It has the benefit of automatically
>quoting your
> values for you. Amongst other benefits, you won't have to remember to automatically
>quote your
> data. For example, some poorly designed Web sites will cras
is done until that handle is cleared.
It is known to be an issue with DBD:JDBC and clearing handles. best to
limit them.
My 2 cents
-Original Message-
From: Curtis Poe [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 06, 2001 6:18 PM
To: CGI Beginners
Subject: RE: This n'
--- Kris Cook <[EMAIL PROTECTED]> wrote:
> Ah. Both are easier. I especially like the here-doc method, which is what
> I should have used. Thanks, Brett.
Might I suggest that you use placeholders? It has the benefit of automatically
quoting your
values for you. Amongst other benefits, you w
MAIL PROTECTED]
> Subject: RE: This n' that
>
>
> On Wed, 6 Jun 2001, Kris Cook wrote:
>
> > Also, I couldn't get my ActivePerl implementation to take
> the $values inside
> > the string. I had to concatenate them with the '.'
> operator, a
On Wed, 6 Jun 2001, Kris Cook wrote:
> Also, I couldn't get my ActivePerl implementation to take the $values inside
> the string. I had to concatenate them with the '.' operator, as follows:
> $sqlstatement = "INSERT INTO Full (freq, loc, desc, freqtype, cat, call, tx)
> VALUES (".$newfreq.", \'
\'".$newloc."\', \'".$newdesc."\',
\'".$newfreqtype."\', \'".$newcat."\', \'".$newcall."\', ".$newtx.")";
> -Original Message-----
> From: Kris Cook [mailto:[EMAIL PROTECTED]]
> Sent: Wedn
All I can suggest here is to have the script display the constructed value
of $sqlstatement. You may find it has an unexpected punctuation, or one of
the values is null (interestingly, ODBC didn't like null values even if they
were OK in the database - very odd). In my case, ODBC kept hurling un
