|
![](/i/fill.gif) |
Invisible <voi### [at] dev null> wrote:
> Personally, I'd import the whole log into a relational database, and
> process it that way. (Or maybe even use a webserver that keeps its logs
> in a database in the first place, rather than a huge flat file.) But
> apparently that's just me...
Talk about an overly complicated solution for a simple problem.
> On the contrary, figuring out how to work grep vs writing a program in a
> language I already know well is likely to take *slightly* more than
> merely a hundred times longer. (Although you could argue that's a
> one-time cost.)
Writing something like "grep 'hello.*there' file.txt" doesn't require a
lot of time or thinking.
> Personally I just dislike scripting languages. I'd rather use a real
> language with propper error checking and so on and so forth. But I guess
> that's just me.
What's the difference between "a scripting language" and "a real language"?
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |