Re: File Format : XML v MySQL / postgres / sqllite

Hi, Just catching up on the archives and came across this thread. I began work about a month ago, for my personal use, of a simple easy-to-use way to quickly get information out of a Gnucash Database: https://github.com/ebridges/accounting-reports Right now it's pretty minimal (balance reports,

Re: File Format : XML v MySQL / postgres / sqllite

Hi, David, Whether PyCash is for an average user really depends on what you consider the average user to be. It is a Python library and, if you don't expect an average user to know how to write Python code then no - it is not for an average user. What it offers, though, is a pure Python interface

Re: File Format : XML v MySQL / postgres / sqllite

It is indeed a python package so typically you write a script. For instance, create the file test_piecash.py with the content # start of the file import piecash book = piecash.open_book("/the/path/to/your/gnucash-book.gncash") for transaction in book.transactions:

Re: File Format : XML v MySQL / postgres / sqllite

Sébastien, I know that users are advised not to edit their Gnucash data directly; is piecash an approved application to edit Gnucash data directly? David On January 28, 2018, at 3:41 PM, Sébastien de Menten wrote: David, This is one of the key reason for piecash to

Re: File Format : XML v MySQL / postgres / sqllite

David, This is one of the key reason for piecash to exist as it does not need any compilation (it is a pure python package) and works even without having gnucash installed. It doesn't use gnucash libraries as it reads (and writes) directly to the gnucash book through SQL. I do not have a Mac so

Re: File Format : XML v MySQL / postgres / sqllite

Sebastien, The problem isn’t with Python (I am told that Macs already have Python on them). The problem as I understand it (John will no doubt correct me when my statements prove ill-informed or flat out wrong) has to do with the fact that GnuCash requires a specific version of Python, which

Re: File Format : XML v MySQL / postgres / sqllite

Hello David, Regarding the use of python on windows and Mac, Anaconda has made a huge difference in the last years providing all packages in an easy precompiled version. You can have a look at https://conda.io/docs/user-guide/install/macos.html for the installation (which is simple and does not

Re: File Format : XML v MySQL / postgres / sqllite

I suspect David was thinking of CuteCash, Christian Stimming’s experimental Qt GUI. Regards, John Ralls > On Jan 27, 2018, at 10:44 AM, Sébastien de Menten wrote: > > Hello David, > > I saw you were mentioning piecash in your message. If you talk about >

Re: File Format : XML v MySQL / postgres / sqllite

Hello David, I saw you were mentioning piecash in your message. If you talk about http://piecash.readthedocs.io/en/latest/, it is not a proof of concept for a frontend but an alternative to the gnucash python bindings to work with gnucash books stored in any of the 3 SQL backends (SQLite,

Re: File Format : XML v MySQL / postgres / sqllite

Mike, There is nothing new as far as I know about the file formats. You are right that the primary benefit to using sql is being able to generate data sets from sql that can used in reports. Processing a data file is no quicker in sql, since it all gets loaded in at start up. Sql, moreover,

Re: File Format : XML v MySQL / postgres / sqllite

I switched from XML to SQLite about a year ago. I perceive a performance improvement on loading, but that’s about it. (and I generally never shut the app down anyway) I haven’t attempted any custom reporting yet, but I plan to. I could be mistaken, but I think PyCash is designed to parse the

File Format : XML v MySQL / postgres / sqllite

Dear All, XML is the default when creating a new file. I have seen various quite dated questions about the decision process of selecting which db to use. I think that the main advantage of using MySQL would be the ability to generate custom reports. Are there any other advantages and are