[EMAIL PROTECTED] wrote:

I remember Jeff saying that a new SQL::Statement has been in the works


Yes, unfortunately delayed. I'm hoping for September now.


From: Matthew O. Persico <[EMAIL PROTECTED]>
The problem was that I had a value that was the empty string, When I generated the SQL, the empty string was represented by consecutive single quotes. When I tried to write to my table
via DBD::CSV, I got an error that looked for all the world as if SQL::Statement mis-parsed consecutive single quotes



A comprehensive fix is coming -- Ian Bjorhovde and Janek Schleicher have submited a patch to Text::CSV_XS which will allow differentiation between a 0-length string and a NULL value. In the meantime, 0-length strings are the same as NULL and treating them as NULL in the SQL probably works better, see the section on NULLs at


http://www.vpservices.com/jeff/programs/sql-compare.html

Or if you don't want to use NULL, using placeholders should solve the parsing problem temporarily.

--
Jeff



Reply via email to