Re: Odd behavior from DBD::CSV

2003-09-04 Thread Scott R. Godin
Unknown Sender wrote: W li?cie z wto, 26-08-2003, godz. 18:33, Jeff Zucker pisze: Well, I thought so, and that's why AnyData works that way. But CSV worked with the \015\012 default when I inherited it and there are too many scripts out there based on that behaviour for me to contemplate

Re: Odd behavior from DBD::CSV

2003-08-28 Thread Ron Savage
On Wed, 27 Aug 2003 14:48:25 +0200, Peter J. Holzer wrote: Hi Peter  my($s) = Data\n\r;  Erm, that should be Data\r\n, at least on MS-DOS/Windows and all  line-oriented Internet protocols I'm familiar with (telnet, smtp,  nntp, http, imap, ...). Nope. It should be \n\r as stated. I knew

Re: Odd behavior from DBD::CSV

2003-08-28 Thread Peter J. Holzer
First, I think Jeff is right. We're getting a bit off-topic here. On 2003-08-28 09:01:59 +1000, Ron Savage wrote: On Wed, 27 Aug 2003 14:48:25 +0200, Peter J. Holzer wrote:  my($s) = Data\n\r;  Erm, that should be Data\r\n, Nope. It should be \n\r as stated. I knew someone would fall

Re: Odd behavior from DBD::CSV

2003-08-27 Thread Waldemar urowski
W licie z wto, 26-08-2003, godz. 18:33, Jeff Zucker pisze: Well, I thought so, and that's why AnyData works that way. But CSV worked with the \015\012 default when I inherited it and there are too many scripts out there based on that behaviour for me to contemplate breaking backward

Re: Odd behavior from DBD::CSV

2003-08-27 Thread Peter J. Holzer
On 2003-08-27 12:06:19 +0200, Waldemar ?urowski wrote: W li?cie z wto, 26-08-2003, godz. 18:33, Jeff Zucker pisze: chomp $line; { local $/ = \r; chomp $line } Would help to remove both \015 and \012, or only \012, or only \015 from the end of a line? Yup. However, while your method may

Re: Odd behavior from DBD::CSV

2003-08-27 Thread Ron Savage
On Wed, 27 Aug 2003 12:38:55 +0200, Peter J. Holzer wrote: Hi Peter  On 2003-08-27 12:06:19 +0200, Waldemar ?urowski wrote:  W li?cie z wto, 26-08-2003, godz. 18:33, Jeff Zucker pisze: chomp  $line; { local $/ = \r; chomp $line }  Would help to remove both \015 and \012, or only \012, or only  

Re: Odd behavior from DBD::CSV

2003-08-27 Thread Peter J. Holzer
On 2003-08-27 21:11:42 +1000, Ron Savage wrote: On Wed, 27 Aug 2003 12:38:55 +0200, Peter J. Holzer wrote:  On 2003-08-27 12:06:19 +0200, Waldemar ?urowski wrote:  chomp  $line; { local $/ = \r; chomp $line }  Would help to remove both \015 and \012, or only \012, or only  \015 from the

Re: Odd behavior from DBD::CSV

2003-08-27 Thread Jeff Zucker
Peter J. Holzer wrote: On 2003-08-27 21:11:42 +1000, Ron Savage wrote: On Wed, 27 Aug 2003 12:38:55 +0200, Peter J. Holzer wrote: On 2003-08-27 12:06:19 +0200, Waldemar ?urowski wrote: [stuff about removing line endings] I'm not sure how any of this relates to DBD::CSV since the module

Re: Odd behavior from DBD::CSV

2003-08-26 Thread Jeff Zucker
Thomas A. Lowery wrote: The default behavior (from the docs) looks carriage return, line feed. csv_csv The attributes csv_eol ... Defaults are \015\012 Right, the default record separater is \015\012, so you need to specifically set the eol to \n if the file uses a platform-specific eol.

Odd behavior from DBD::CSV

2003-08-25 Thread Thomas A. Lowery
Jeff, I'm adding more support for csv in DBI::Shell. However, I'm seeing some odd results. If I use this connection string and query. 0 Rows are fetched. (some code removed for brevity) my $dbh = DBI-connect(DBI:CSV:f_dir=.) ... my $sth = $dbh-prepare(select