Reply to post: Typos in text files...

It's always DNS, especially when a sysadmin makes a hash of their semicolons

Karl Vegar

Typos in text files...

Have had some brushes with typos in text files that are automagically imported.

Though not the vital service killing kind.

Once uppon a time (early noughtys) I was working on / inherrited a web service to present financial data. This data was entered using a dos "application", exported to a CVS like file, using | as the only delimiter, passed on to my system over the internjet, and then imported into my system. The closest thing this had to any kind of validation, was the db schema.

Every now and again, someone would misstype 1 as |. And this would not be overly visible in the DOS application. Export would not be troubled by this at all, file transfer would naturally not notice at all. The import would fail with a note to the logs, and if I didn't notice the logs, the client would complain about stale data after a couple of days.

When the logs were showing error at line 3'254 I coule easily use * text editor, and fix it easily enough. However, when got to complaining about line 325'400, I learned to love SED.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon