Up Prev Next
From: "Scott Zetlan" <scottzetlan at aol dot com>
Subject: RE: A patch proposal to the NULL-value problem on blk_rowxfer
Date: Jun 20 2002 9:35PM
Hmm -- I seem to recall that Sybase::BCP and Sybase::BLK will both assume
empty strings are null values unless you set a NULL_PATTERN option during
config. However, I will have to check on that.
> -----Original Message-----
> From: owner-SYBPERL-L@list.cren.net
> [mailto:owner-SYBPERL-L@list.cren.net]On Behalf Of Michael Peppler
> Sent: Thursday, June 20, 2002 5:21 PM
> To: SybPerl Discussion List
> Subject: Re: A patch proposal to the NULL-value problem on blk_rowxfer
> On Thu, 2002-06-20 at 08:53, Masatsuyo Takahashi wrote:
> > To summarize,
> > [Rule1] undef is the only value that is converted to NULL.
> > [Rule2] defined values are always also defined values in Sybase
> I think that that is consistent.
> > You have to be aware of the fact that you get DEFINED values
> > (i.e. ""s) when you split a CSV line such as
> > ,,,,,
> > which doesn't seem to define any values.
> Indeed. I *think* that Sybase::BCP and/or Sybase::BLK will do the
> "right" thing here, but I may be wrong.