From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] web-based plan 9?
Date: Fri, 21 Nov 2008 12:18:48 -0500 [thread overview]
Message-ID: <031b381fadb797cae6506e8db8b1285f@quanstro.net> (raw)
In-Reply-To: <e1d437a40811210905h3472f836rc3d61fb323a30ba4@mail.gmail.com>
> - a "ctrl" file which accept only COMMIT, ROLLBACK and ABORT
> - an "error" file
> - a "notice" file (postgresql has RAISE NOTICE... may be others have it
> too)
> - a "data" file (append only in the transaction, but not outside) where
> the INSERT, UPDATES, DELETE and all the DDL and DCL commands will be written
> - each SELECT have to be written in a different file (named
databases seem pretty far outside 9fans territory and design
on a mailing list doesn't seem like a good idea ... but anway,
i hope this comment is more strategy than design and a bit
more general.
since a relational database isn't imperative thing, i have never
understood having a imperative interface to one, especially an
unconstrained interface. if you have a problem big enough to
warrant a database, it will get refactored, rekeyed, renormaled &c. it's
quite unattractive to have a database reorganization escape
and force changes in imperative code. i think a declarative
interface would make much more sense — as in i want a new
user fred with properties x, y, z instead of begin transaction ....
if you're going to put up with a database, it needs be a big boy
and take care of itself. would you put up with a file system
that required you to do the locking and inode allocation yourself?
- erik
next prev parent reply other threads:[~2008-11-21 17:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 1:35 Pietro Gagliardi
2008-11-20 14:25 ` Eric Van Hensbergen
2008-11-20 14:37 ` Fco. J. Ballesteros
2008-11-20 14:47 ` Eric Van Hensbergen
2008-11-20 15:07 ` Fco. J. Ballesteros
2008-11-20 15:16 ` Eric Van Hensbergen
2008-11-20 15:21 ` Francisco J Ballesteros
2008-11-20 14:51 ` erik quanstrom
2008-11-20 18:59 ` Skip Tavakkolian
2008-11-20 19:25 ` Skip Tavakkolian
2008-11-20 22:15 ` Giacomo Tesio
2008-11-20 23:18 ` Skip Tavakkolian
2008-11-21 5:19 ` lucio
2008-11-21 10:15 ` Giacomo Tesio
2008-11-21 11:55 ` matt
2008-11-21 14:01 ` Tom Lieber
2008-11-21 14:34 ` matt
2008-11-21 15:13 ` Giacomo Tesio
2008-11-21 15:53 ` matt
2008-11-21 16:05 ` erik quanstrom
2008-11-21 17:05 ` Giacomo Tesio
2008-11-21 17:18 ` erik quanstrom [this message]
2008-11-22 20:15 ` Giacomo Tesio
2008-11-21 17:24 ` matt
2008-11-21 18:12 ` a
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=031b381fadb797cae6506e8db8b1285f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).