From: Andrew Hume <andrew@humeweb.com>
To: John Gilmore <gnu@toad.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] cut, paste, join, etc.
Date: Wed, 17 Feb 2021 06:52:57 -0800 [thread overview]
Message-ID: <C1580473-3943-4007-A791-0FBAF217B5DC@humeweb.com> (raw)
In-Reply-To: <21803.1613556854@hop.toad.com>
daytona was always a separate commercial product.
it was an extremely large, very efficient database.
you should think of it as analogous to a large postgres system.
rick greer was the primary author; an overview paper is
http://www09.sigmod.org/sigmod/sigmod99/eproceedings/papers/greer.pdf
for many years, probably now as well, it was the main way that
at&t stored per-call information. as of the mid 2000s, it had over 2 trillion
calls in it.
> On Feb 17, 2021, at 2:14 AM, John Gilmore <gnu@toad.com> wrote:
>
> Grant Taylor via TUHS <tuhs@minnie.tuhs.org> wrote:
>> I don't know where the line is to transition from stock text files and
>> an actual DB. I naively suspect that by the time you need an index, you
>> should have transitioned to a DB.
>
> Didn't AT&T Research at some point write a database, called Daytona,
> that worked like ordinary Unix commands? E.g. it just sat there in disk
> files when you weren't using it. There was no "database server". When
> you wanted to do some operation on it, you ran a command, which read the
> database and did what you wanted and wrote out results and stopped and
> returned to the shell prompt. How novel!
>
> Supposedly it had high performance on large collections of data,
> with millions or billions of records. Things like telephone billing
> data.
>
> I found a couple of conference papers about it, but never saw specs for
> it, not even man pages. How did Daytona fit into Unix history? Was
> it ever part of a Unix release?
>
> John
>
next prev parent reply other threads:[~2021-02-17 15:17 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 [this message]
2021-02-17 23:58 ` Dan Cross
2021-02-17 20:49 ` Dave Horsfall
2021-02-22 5:57 ` Tomasz Rola
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=C1580473-3943-4007-A791-0FBAF217B5DC@humeweb.com \
--to=andrew@humeweb.com \
--cc=gnu@toad.com \
--cc=tuhs@minnie.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).