Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

runrig (3385)

runrig
  dougwNO@SPAMcpan.org

Just another perl hacker somewhere near Disneyland

I have this homenode [perlmonks.org] of little consequence on Perl Monks [perlmonks.org] that you probably have no interest in whatsoever.

I also have some modules [cpan.org] on CPAN [cpan.org] some of which are marginally [cpan.org] more [cpan.org] useful [cpan.org] than others.

Journal of runrig (3385)

Thursday May 22, 2003
12:01 PM

Perl saved my bacon

[ #12378 ]
It was all my fault. At a client site, I did some sql updates 'where field_name is not null'. Shoulda been 'where field_name is null'. Luckily, I unloaded the table before and after the updates. I could probably just drop and reload the entire table, but that makes me a bit uncomfortable (more uncomfortable than the screwup I just did). Unfortunately, the client doesn't have perl installed. So I uucp the unload files to my box (anyone else still use uucp?), look for only the records I changed, and generate some sql to change'em back. When I first did the updates, it said about 25,000 rows were updated, which included rows where the old values were the same as the new values. It turned out there were only about 300 rows that were actually changed.

I think only about 3 of our customers have perl installed; I wish they all did. And I wish we had ssh/scp access to all of them too...(though one of them still allows telnet access...eek).

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.