Pat Spinler <[EMAIL PROTECTED]> writes:
> I can't speak for Rob Coker, but I'm only talking about making a SQL
> backend a "one of many" option, and probably not the default one for
> all the reasons you mention.
One possibility is to use a non-client-server SQL engine over a simple file
format. I'm not sure if equivalent engines exist for guile but in Perl there
are DBD::File and DBD::CSV drivers for the DBI switch for flat files, and
comma separated value files. This way you could use simple text files or DB
files by default, but give the user a dialog that let them select a database
backend if they wanted.
The really nice thing about using an abstract switch like this is that no
other portions of the code need have branches for different drivers, they all
use the SQL engine and uses straight standard SQL. Ok, so "standard" SQL is a
bit of a myth, but probably gnucash wouldn't have to do too many tricky things
and could probably get away with a pretty portable subset of SQL.
I really like this idea, but shouldn't we concentrate on getting a stable
version of the current infrastructure out and widely used before we start
ripping the whole thing apart all over again?
--
greg
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
