From: "Giacomo Tesio" <giacomo@tesio.it>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] dbfs and web framework for plan 9
Date: Mon, 24 Nov 2008 15:13:22 +0100 [thread overview]
Message-ID: <e1d437a40811240613k32f9f66ch151fd76986c9ecd5@mail.gmail.com> (raw)
In-Reply-To: <492A88DD.2070900@proweb.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
On Mon, Nov 24, 2008 at 11:58 AM, matt <mattmobile@proweb.co.uk> wrote:
>
> That's exactly what constraints, rules in SQL etc are for. Maybe some
>> similar ruling system for filesystems would be fine :)
>> (any suggestions ?)
>>
>>
> That's what I was driving at. To map SQL <> FS you end up replicating lots
> of SQL logic in your client FS. Reads are *always* out of date. Writes can
> happen across tables but need to be atomic and able to roll back.
>
Probably I was not clear on what I'm thinking about.
I think that rebuild a relational database on a filesystem is (quite)
pointless.
What I'm proposing is to design/develop the interface to interact with
(any?) rdbms through a filesystem.
A kind of "proxy" to the db with a filesystem interface.
A "draft" could be (even if I've already found some problems in it):
> - 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
>
> The problems:
- transaction -> directory conversion require creating a new connection
to the backend (if I'm right thinking that transaction are connection wide)
- xml output of fetchable results (SELECT, FETCH, SHOW...) require a tool
to easily query such an output. It seem Plan 9 miss such a tool. xmlfs
actually is unsuitable.
(I'm thinking about an xpath command accepting xml in stdin and the xpath
query as an argument, and return to stdout the results)
Giacomo
[-- Attachment #2: Type: text/html, Size: 2937 bytes --]
prev parent reply other threads:[~2008-11-24 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 18:58 [9fans] dbfs and web framework for plan 9 (was: web-based plan 9?) Giacomo Tesio
2008-11-23 22:06 ` Enrico Weigelt
2008-11-23 22:26 ` Francisco J Ballesteros
2008-11-23 22:50 ` Enrico Weigelt
2008-11-24 9:27 ` Giacomo Tesio
2008-11-24 9:30 ` Giacomo Tesio
2008-11-24 10:58 ` [9fans] dbfs and web framework for plan 9 matt
2008-11-24 14:13 ` Giacomo Tesio [this message]
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=e1d437a40811240613k32f9f66ch151fd76986c9ecd5@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).