Re: 'Theoretical' DB OS

From: David Portas <REMOVE_BEFORE_REPLYING_dportas_at_acm.org>
Date: 24 Mar 2007 11:52:48 -0700
Message-ID: <1174762368.128260.39630_at_l77g2000hsb.googlegroups.com>


On 24 Mar, 02:34, christianlo..._at_yahoo.com wrote:
> I'm working on a conceptual model (ie 'thinking about' / 'air code')
> to implement a small operating system (extensible of course) that is
> built completely out of a common set of database functions.
>
> The specific question I have now is an important one - how should I
> store files?
>
> Heh. It's theory about what is the best physical implementation. ;)
>
> My first guess is that each attribute gets it's own file. Should I
> make it where the user can select whether he wants it to be stored
> fixed width or delimited?
>

Why do you want the database to be part of a file system at all? If the database was not exposed to the file system then the security, storage management and physical data integrity could be controlled exclusively by the DBMS. Possibly that approach has some advantages.

--
David Portas
Received on Sat Mar 24 2007 - 19:52:48 CET

Original text of this message