On 2006-09-26 12:51:35 -0700, Pai Peng wrote: > In my project I first prepare an INSERT statement 'INSERT INTO table > (col1, col2, col3, ...) VALUES (?, ?, ?, ...)' once, then insert > multiple records using 'execute(@values)'. The problem is that not all > values of all columns are available. So I should either leave them empty > or set them as default values. I try to use 'NULL' or 'DEFAULT' for > those unavailable values in '@values', but it didn't work.
That would insert the literal string 'NULL' or 'DEFAULT'. To insert a
null value, use undef.
hp
--
_ | Peter J. Holzer | If I wanted to be "academically correct",
|_|_) | Sysadmin WSR | I'd be programming in Java.
| | | [EMAIL PROTECTED] | I don't, and I'm not.
__/ | http://www.hjp.at/ | -- Jesse Erlbaum on dbi-users
pgpRbHu6q8xvM.pgp
Description: PGP signature
