sqlite file format, anyone?

[Derek Atkins]

linas at linas.org (Linas Vepstas) writes:

> Besides, the pg backend 'works' today; it doesn't have business object
> support, but I'm thinking that with 'setters', it might not be hard to
> add business object support.

"Setters" as you keep calling them are completely irrelevant.  What
we need are hooks for the BackendRegistry, and we need to completely
re-write the Query* -> SQL conversion.  I already added comments
in the PG code for where we'd need hooks into the BackendRegistry...

And then we'd need to implement the PGBackendAPI plugin for each of
the objects to add.

> > Matthew's work
> 
> Well, I suspect that this is really what we are talking about, isn't it?

Isn't it?  It's what I've always been talking about.  The current code
doesn't have a clean separation (IMHO) between PG-specific and
SQL-generic code.  Matthew was planning to fix that.  Also, Matthew
does DB design for a living, so I do trust that he knows what he's
talking about (certainly more than I do ;)

Another thing we need to do is rename the existing gncEntry table (to
gncSplit, or "Split), because there is another object (in the business
code) named gncEntry.  If Splits were to be called Entries then they
should have been globally renamed, not just renamed in the PG backend.

Personally, I think table-name should equal the GNC_ID_ string for any
object..

> --linas

-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 at MIT.EDU                        PGP key available