DB design document

[Derek Atkins]

David Merrill <dmerrill@lupercalia.net> writes:

> Is it possible that the answer is to take the existing engine code and
> separate the Query API into calls into a corresponding API on the
> server side? I'm still getting familiar with the code, so I have only
> a vague concept of its functions. But obviously the existing Query API
> is working.

I think the Query API is only part of what we need.  Yes, we can use
the Query API and have it "execute" on the server, indeed that was my
plan.  However, we would still need the APIs to "write" changes to the
data store (add/delete/modify splits/accounts/groups, etc.).

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available