From: Tomasz Rola <rtomek@ceti.pl>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] cut, paste, join, etc.
Date: Mon, 22 Feb 2021 06:57:17 +0100 [thread overview]
Message-ID: <20210222055717.GA28147@tau1.ceti.pl> (raw)
In-Reply-To: <55d60220-c22d-c99f-f40c-68a741183213@gmail.com>
On Tue, Feb 16, 2021 at 08:26:11PM -0600, Will Senn wrote:
[...]
> Oops. That's right, no username & password, but you still need to
> bring it up and interact with it... accept, as you say, you can
> enter your sql as an argument to the executable. OK, I suppose ...
> grump, grump... Not quite what I was thinking, but I'd be hard
> pressed to argue the difference between creating a handful of files
> in the filesystem (vs tables in sqlite) and then using some unix
> filter utilities to access and combine the file relations (vs
> passing sql to sqlite) other than, it'd be fun if there were select,
> col, row (grep?), join (inner, outer, natural), utils that worked
> with text without the need to worry about the finickiness of the
> database (don't stone me as a database unbeliever, I've used plenty
> in my day).
I am not sure if this is what you are looking for, but sections 3 and
4 of "The AWK Programming Language" (by Aho, Kernighan and Weinberger)
have a description of very nice data processing scripts written in
AWK. Might even work in gawk. Might even work, actually - I had no
time to write the code into files and give it a try.
Personally, I would rather use awk for this rather than multiple
command line utilities. Might be a bit nicer to modern system with
process accounting enabled (I once wrote a shell script processing
mailbox files, plenty of echos and greps, but since then have seen the
light and I repented). On the other hand, on multiprocessor computer,
each part of pipe runs in parallel, but I guess this had been said
already.
Also, found this in my notes - if you, or anybody from a future would
like a quick glimpse on "what awk":
:: Drinking coffee with AWK
https://lobste.rs/s/hdljia/drinking_coffee_with_awk
https://opensource.com/article/19/2/drinking-coffee-awk
:: Using AWK and R to parse 25tb
https://lobste.rs/s/kgah5l/using_awk_r_parse_25tb
https://livefreeordichotomize.com/2019/06/04/using_awk_and_r_to_parse_25tb/
--
Regards,
Tomasz Rola
--
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** **
** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
next prev parent reply other threads:[~2021-02-22 6:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 1:08 M Douglas McIlroy
2021-02-17 1:16 ` Will Senn
2021-02-17 1:43 ` Grant Taylor via TUHS
2021-02-17 2:26 ` Will Senn
2021-02-17 4:08 ` Grant Taylor via TUHS
2021-02-17 10:14 ` John Gilmore
2021-02-17 14:52 ` Andrew Hume
2021-02-17 23:58 ` Dan Cross
2021-02-17 20:49 ` Dave Horsfall
2021-02-22 5:57 ` Tomasz Rola [this message]
2021-02-17 3:29 ` John Cowan
-- strict thread matches above, loose matches on Subject: below --
2021-02-18 20:20 Brian Walden
2021-02-18 20:41 ` Anthony Martin
2021-02-16 20:33 Will Senn
2021-02-16 21:02 ` Dave Horsfall
2021-02-16 21:15 ` Will Senn
2021-02-16 21:26 ` Dave Horsfall
2021-02-16 21:06 ` Dennis Boone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210222055717.GA28147@tau1.ceti.pl \
--to=rtomek@ceti.pl \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).