GnuCash PostgreSQL support

[Colin Law]

On 27 January 2012 15:48, Tarlika Elisabeth Schmitz
<gnucash5 at numerixtechnology.de> wrote:
> On Fri, 27 Jan 2012 09:57:56 -0500
> Derek Atkins <warlord at MIT.EDU> wrote:
>
>> There are a LOT of data loss issues in
>>the SQL backend that have been fixed in later releases.  You do NOT
>>want to use 2.4.4 with SQL.  You want at least 2.4.9 if not the (just
>>released) 2.4.10.  And even there you might still find some data loss
>>issues with SQL.
>
> Thanks for the warning, Derek.
>
> In other words, GnuCash with SQL is not stable for real-world use at
> the moment.
>
> I had so much been looking forward to moving to SQL for three reasons:
>
> 1) speed (not too important)
>
> 2) being able to extract my own reports via SQL

I do this by normally running with xml but doing a Save As to MySQL at
the end of each month and running the reports there.  Make sure to go
back to xml file after this though as gnucash will by default open the
database on next opening.  I avoid this possibility by starting
gnucash with a desktop shortcut that explicitly opens the xml file by
specifying it on the command line.

>
> 3) I want to bulk modify 1000s of transactions (I know it's not
> recommended to tamper with the data directly and I'd do a backup
> beforehand). For instance, I want to transpose Description and Notes of
> certain transactions (so they show up in the reconcile window). I have
> 8 years worth of data, 55MB xml and I'd like to restructure the way I
> record some expenses based on my notes.

Maybe best to wait a bit before doing this.  You could still save as
db format, run your updates, and go back to xml, but there might be a
small risk at the moment of losing something along the way I suppose.

Colin