I'd add another level of paranoia and make a backup to yet a
different name because if you run this twice with a bug
then you've overwritten your good backup.
Assuming you can ensure that this is good CSV format
you can also attack these files as if they were SQL databases
by using DBI and DBD::CSV or DBD::RAM. If the files
are really long DBD::RAM may be the best because it looks like
it can refrain from reading the whole file into memory.
But for not so huge files the above strategy is probably
fastest.
You probably want to do some tests or just monitor the output
on the screen, in case you have bad data (maybe embedded commas?)
which could throw off the routine.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.