Correct, but he he building dynamic SQL. The resulting insert statement's values clause looks like (v1,v1,,v4...); the problem is the ",,".
This is why I suggested to use bind variables. ----------------- Ron Reidy Senior DBA Array BioPharma, Inc. -----Original Message----- From: amonotod [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 2:04 PM To: [EMAIL PROTECTED] Cc: Ronald J Kimball; 'Hardy Merrill' Subject: RE: SQL- Insert problem > From: "Ronald J Kimball" <[EMAIL PROTECTED]> > Date: 2004/08/13 Fri PM 05:59:39 GMT > > Hardy Merrill [mailto:[EMAIL PROTECTED] wrote: > > > > Just in case the op doesn't make the connection, he needs to test his > > variables for undef before the execute, and if one is undef, then put > > Why does he need to do that? I have never had to test my bind values for > defined-ness when using placeholders. An undef in Perl becomes a NULL in > Oracle, and vice versa. Programming the Perl DBI, Page 221, paragragh 1, sentence 3: "Undefined values or 'undef' can be used to indicate null values." > Ronald HTH, amonotod -- `\|||/ amonotod@ | sun|perl|windows (@@) charter.net | sysadmin|dba ooO_(_)_Ooo____________________________________ _____|_____|_____|_____|_____|_____|_____|_____| This electronic message transmission is a PRIVATE communication which contains information which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender of the delivery error by replying to this message, or notify us by telephone (877-633-2436, ext. 0), and then delete it from your system.
