From: diaz@x.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 Relational Databases
Date: Thu, 8 Feb 2001 15:15:07 -0500 [thread overview]
Message-ID: <20010208201814.5990119AD4@mail.cse.psu.edu> (raw)
> A couple of months ago, Bill Staniewicz asked about what RDBMSs are
> used in plan9 if any. I didn't see anyone respond to this, but all I
> have seen is the following:
I responded to Bill directly and should have sent this out to the list.
At the bottom of the distribution page is a tar file for 'pq'.
It is an "implicit" rdb in that joins are done across the relations
dynamically. You create your relations and describe the schemata
in a dispatch file. When queries are made the join code figures
out the best way to link the relations to resolve the query.
It also (cleanly) supports distributed relations.
It has a lot of flexibility and power, and more functionality
than my hastily put together documentation describes.
It has seen a lot of heavy, production use over the years
in a variety of applications. As an example, one directory
application currently supports 20 million lookups per month.
The distribution includes a sample set of relations you can
experiment with, man pages, etc.
Finally, I have to say that despite the attribution on the web page,
pq is the work of Michael Baldwin (who is now at Vita Nuova -
baldwin@vitanuova.com). I merely packaged it up.
Given that, I'd be happy to answer any questions you may
have.
Hope you find it useful.
next reply other threads:[~2001-02-08 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 20:15 diaz [this message]
2001-02-09 2:01 ` Ish Rattan
2001-02-09 2:18 ` [9fans] " Vincent D Murphy
2001-02-09 9:40 ` [9fans] " nw
2001-02-09 9:41 ` vecera
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 16:40 William Staniewicz
2001-02-09 14:40 William Staniewicz
2001-02-08 18:57 Mark Otto
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=20010208201814.5990119AD4@mail.cse.psu.edu \
--to=diaz@x.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).