Christopher Browne wrote:
> The situation is worsened when there isn't anyone to be a DBA; the DBMSes
> that are available on Linux are largely not all that "management free."
I have to bow to your knowledge here. I've not yet worked extensively
in any of the free linux db's. Just downloaded postscript 6.5.2
tonight, though. We'll see where that goes.
> > For the purposes of getting GnuCash to use a db store, I'd be willing to
> > make a script to create a small database for gnucash in, say, postgresql
> > if anyone wanted it. Then this could just be included with the
> > distribution as part of our install process.
>
> It gets scary real quick:
> a) My install isn't in the precise location that your script expects.
> Presumably a good script can search for where it should find PostgreSQL;
> this is not the big problem.
>
> b) But I want to customize this a bit and connect to PostgreSQL on another
> box.
>
> This makes life quite bad immediately, as there's more config involved,
> and the bad part is that if the default installation "protocol" is
> strongly oriented towards "local PostgreSQL," it may prove quite a
> pain to recustomize for "my configuration."
Well, yeah, but is that really important ? After all, if you know
enough to set up a db with the appropriate schema remotely, or in a
non-default location, you're already a pretty sofisticated user. As
long as what we require is well documented, let 'em.
Also - it's perfectly fair for us to require a certain setup. "Hey, if
you wanna do a postgresql account store, here's the way it'll be."
After all, gnucash in essance does that now. I can't for instance,
store different accounts in different directories, or change the
filenames it uses, or tell it to use one file per account, or ...
(I've only been keeping my accounts in gnucash for ~3 months, and I
already have 163 data files. Yoip !)
-- Pat
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
