From: Hans Reiser <reiser@namesys.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: WinFS delayed, this probably means more time for semi-structured
Date: Tue, 13 May 2003 14:53:54 +0400 [thread overview]
Message-ID: <3EC0CEC2.706@namesys.com> (raw)
WinFS delayed, this probably means more time for semi-structured query languages
to establish themselves instead of SQL
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
SQL would be just terrible for FS semantics to standardize on, and
hopefully we will be able to deploy a semi-structured querying language
alternative (www.namesys.com/whitepaper.html) before they ship. I was
sort of expecting that they would be late, as they don't yet have a good
technical foundation in their FS storage layer for adding database
functionality, and we surely know that's a lot of work to create;-).
http://www.theregister.co.uk/content/4/30670.html
--
Hans
reply other threads:[~2003-05-13 10:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EC0CEC2.706@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.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).