From: "Giacomo Tesio" <giacomo@tesio.it>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] web-based plan 9?
Date: Fri, 21 Nov 2008 18:05:08 +0100 [thread overview]
Message-ID: <e1d437a40811210905h3472f836rc3d61fb323a30ba4@mail.gmail.com> (raw)
In-Reply-To: <4926D977.2080900@proweb.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
>
> I'd like to know how do you would map the operations to the filesystem.
>>
>>
> one directory per queryset row returned (possibly named by the primary
> key), one file per column
>
Ok... I read it somewhere in the archives of the list.
But I found it a little "inadeguate":
- what about multiple fields primary key?
- what about transactions?
- what data modifications (insert update delete)?
'till now I imagine it so:
opening a transaction could be creating a directory on a dbfs/transactions/
each of such directories (like the complete connection) has
- 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
sequentially): after writing the query, the same file could be read to get
the results (in xml...)
- on errors, sequents writes fails and error file will be readable
>
> Query result in a filesystem hierachy would be a pain... xml would be
>> better, since you could transform it quickly.
>> BTW, there should be an xmlfs project waiting somewhere...
>>
>
> ah xml, the ultimate 2d grid !
I'm missing what you mean.
xlmfs is bugged?
Giacomo
[-- Attachment #2: Type: text/html, Size: 2276 bytes --]
next prev parent reply other threads:[~2008-11-21 17:05 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 [this message]
2008-11-21 17:18 ` erik quanstrom
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=e1d437a40811210905h3472f836rc3d61fb323a30ba4@mail.gmail.com \
--to=giacomo@tesio.it \
--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).