in reply to Re^13: Sybase BCP date formatter
in thread Sybase BCP date formatter

I'm sure the change is made somewhere in the following part. I've tried this
s/(^|\,)($mon_re)\s{1,2}(\d{1,2})\s(\d{4})\s\s?(\d\d?):(\d\d):(\ +d\d):(\d{3})([AP])M(\,|$)/ $1 . sprintf( '%04d %02d %02d %02d:%02d%03d',
I can't figure out where the variable for (A/P)M get get loaded. In my mod the output shows the date as: ,1997 01 28 09:53022, I'm looking for ,1 28 1997 09:53AM,

Replies are listed 'Best First'.
Re^15: Sybase BCP date formatter
by Corion (Patriarch) on Dec 17, 2008 at 15:11 UTC

    Read perlre and perlop about s/// and the /e switch. This will give you the information you need to find out where the variables $1 to $9 get loaded. Also, you might be interested in the strftime function of the POSIX module, which has convenient functions to create date/time strings. Even moreso, I recommend staying with the given format YYYY-mm-dd HH:MM:SS instead of using something else.

          Ok... I've muddled along here and am getting a bit closer to what I need.
          #!/usr/bin/perl use strict; use warnings; { my %mons = qw( Jan 1 Feb 2 Mar 3 Apr 4 May 5 Jun 6 Jul 7 Aug 8 Sep + 9 Oct 10 Nov 11 Dec 12 ); my $mon_str = join '|', keys %mons; my $mon_re = qr/$mon_str/; sub fix_bcp_file { my ( $file ) = @_; local ( $^I, @ARGV ) = ( '.bak', $file ); while ( <> ) { s/(^|\,)($mon_re)\s{1,2}(\d{1,2})\s(\d{4})\s\s?(\d\d?):(\d +\d):(\d\d):(\d{3})([AP])M(\,|$)/ $1 . sprintf( '%02d %02d %04d %02d:%02d%sM', $mons{ $2 }, $3, $4, $5, $6, $9 ) . $10 /eg; print; # UPDATED thanks runrig } } } for my $file (@ARGV) { fix_bcp_file($file); }
          So from my test data which is:
          0960280645060099800,1,0,1,03/01/200003240685/0960280645060099800_1,,,,52688,Jan 28 1997 9:53:22:610AM,200003240685
          My script will now convert to:
          0960280645060099800,1,0,1,03/01/200003240685/0960280645060099800_1,,,,52688,01 28 1997 09:53AM,200003240685

          Can someone suggest how I can get rid of leading zero's without creating a space?

          Rob (...on a steep learning curve...)