'Theoretical' DB OS

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?

Please note that it's difficult for me to understand some terms, so please define your terms if you use anything more than key, relation, tuple, and attribute. Thanks.

Christian Received on Fri Mar 23 2007 - 21:34:12 CDT