I've written a quick and dirty script to change a comma seperated DB dump to a tab delimited file for importing. Here's the code:

my $log_file = "/c/mysql.out";
my $out_file = "/c/mysql.dshield";
open LOG, "$log_file" || die "Can't open log file: $!";
open OUT, ">$out_file" || die "Can't open output file: $!";
while (<LOG>) {
        s/,/\t/g;
    print OUT $_;
    }
close OUT || die "Can't close the output file: $!";
close LOG || die "Can't close the log file: $!";
[download]

Here's a snippet of what it's parsing:

2005-07-06 00:00:00-05:00,85099794,1,202.97.174.226,1038,192.168.1.20, 1434,udp,

Here's what is dumped out after the script chews it up:

2005-07-06 00:00:00 -05:00 85099794 1 202.97.174.226 1038192.168.1.20 1434 udp

So, why would this miss replacing the third from last comma with a tab? It simply deletes the comma without replacement. I can't figure this out! Help please?? Monger

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.