gnucash-1.8.0 and Postgres Backend
Matthew Vanecek
mevanecek at yahoo.com
Tue Feb 4 18:24:49 CST 2003
On Mon, 2003-02-03 at 15:51, Klaus Dahlke wrote:
> Hi all,
>
> a few days ago it was mewntioned in one of the communicatios here that the postgres backend for gnucash-1.8.0 is somewhat under construction, e.g. recurring transactions are not supperted yet. I like to continue using the postgres backend. Can someone give anupdate on the status?
>
> Thanks.
> Klaus
> _______________________________________________
The Postgres backend *works*. It does not, however, support any of the
new functionality (e.g., Scheduled Transactions, business functions, et
al). Stuff that existed in 1.6.x should still work normally (e.g.,
stocks, price quotes, ledger entry). Note that working from a remote
Postgresql server over TCP/IP may be a bit slower than working with a
local database.
I've not seen any un-fixed crashes due to the Postgresql back-end code,
nor have I seen data lost. I *have* seen instances where Gnucash
crashes, and data is not rolled back by the server. Specifically I
noted that behavior when using the QIF importer while it was being
worked on. You'd enter all the relevant info, match accounts, etc.,
select the appropriate currency, then hit "next", and Gnucash would
crash. The temporary accounts created for the transaction matching were
left in the database, instead of being rolled back/deleted as they are
in a successful completion.
Other than that, it seems to work OK.
--
Matthew Vanecek
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
********************************************************************************
For 93 million miles, there is nothing between the sun and my shadow except me.
I'm always getting in the way of something...
More information about the gnucash-user
mailing list