in reply to DBI: passing undef as an argument

I guess the question to ask is why? You really want NULL right? Perhaps the ODBC driver is not doing what DBI docs say, converting undef to NULL, so perhaps you need a non-placeholder SQL statement to insert a NULL there.

HTH,
SSF

Replies are listed 'Best First'.
Re^2: DBI: passing undef as an argument
by dsheroh (Monsignor) on Aug 08, 2009 at 09:58 UTC
    That doesn't seem likely to me, as OP states that ->execute(undef), on the same prepared statement, does work for him.

    On the other hand, though, I don't have any better theory...

    fws, does the ->execute($Array[0]) version die with just "ODBC error" or does the error message contain any additional information?