DB design document

[David Merrill]

Please take a look at the latest revision of my design document and
give me some feedback.

Some of the issues I'm dealing with:

1. Architecture: A big, fuzzy cloud right now.
2. Security: Lots of questions, few answers. Among the questions,
encryption over the wire, locking down the db itself (depends on the
db), and managing user permissions on some kind of capabilities model
tbd.
3. Table Schemas: Gaping holes.
I have quite a few questions about various fields that are marked with
question marks in the design document. Would you please take  look at
it and give me some feedback?
4. Auditing mechanism needs to be established. I wrote a proposal.
5. "Closing" the books. How? When? Override by "manager" or some other
higher level of access than a "user"?


http://www.lupercalia.net/schema.txt


TIA,
David

-- 
Dr. David C. Merrill                     http://www.lupercalia.net
Linux Documentation Project                dmerrill@lupercalia.net
Collection Editor & Coordinator            http://www.linuxdoc.org
                                       Finger me for my public key

economist, n:
	Someone who's good with figures, but doesn't have enough
	personality to become an accountant.