On 03/16/2005 09:50 AM, NIPP, SCOTT V (SBCSI) said:
Still banging my head into a wall... Now I am getting NULLs
inserted as expected into the database, but I am getting errors on the
compare.
my @old = $test->fetchrow_array ();
foreach $n (0..20) {
chomp($file_val = $data[$n]
c.com
-Original Message-
From: Jeff Zucker [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 11:49 AM
Cc: dbi-users@perl.org
Subject: Re: NULLs in Text::CSV_XS and DBD::CSV
Jeff Zucker wrote:
> 1,,2
> 1,"",2
>
In case I was unclear: the first is three fie
Jeff Zucker wrote:
1,,2
1,"",2
In case I was unclear: the first is three fields with the second field
NULL, the second is three fields with the second field an empty string.
--
Jeff
Ronald J Kimball wrote:
Jeff Zucker [mailto:[EMAIL PROTECTED] wrote:
Yes, currently Text::CSV_XS returns empty string for both empty strings
and NULLs. I am considering providing an option to differentiate the
two and return undef for NULLs.
How do you distinguish between empty string and
Jeff Zucker wrote:
I forgot to mention that DBD::AnyData (which also handles CSV and "pipe
delimited" formats) returns undef for NULL, so if you use DBD::AnyData
or plain AnyData you can get the undefs you want.
Using plain AnyData, this will generate use of unitialized value warning
for all NU
> -Original Message-
Jeff Zucker [mailto:[EMAIL PROTECTED] wrote:
> Yes, currently Text::CSV_XS returns empty string for both empty strings
> and NULLs. I am considering providing an option to differentiate the
> two and return undef for NULLs.
How do you distinguish between empty stri
