On 5/31/19 12:47 PM, John Ralls wrote:
On May 31, 2019, at 8:51 AM, Christopher Singley wrote:
On 5/31/19 9:58 AM, John Ralls wrote:
The GnuCash API documentation is generated by Doxygen. Some parts are
documented better than others. It's built nightly and may be found at
> On May 31, 2019, at 8:51 AM, Christopher Singley wrote:
>
> On 5/31/19 9:58 AM, John Ralls wrote:
>> The GnuCash API documentation is generated by Doxygen. Some parts are
>> documented better than others. It's built nightly and may be found at
>> https://code.gnucash.org/docs/MAINT.
>>
Hello Christopher
I am the dev of piecash. Regarding the second resolution of datetime, I
think I got it by reverse engineering the SQL database format for gnucash
books (you can check by introspecting the DB or the XML). Why do you need
this very high resolution? I think most of the datetime
On 5/31/19 9:58 AM, John Ralls wrote:
The GnuCash API documentation is generated by Doxygen. Some parts are
documented better than others. It's built nightly and may be found at
https://code.gnucash.org/docs/MAINT.
Regards,
John Ralls
If I want to find, say, gnc_account_imap_find_account(),
> On May 31, 2019, at 4:32 AM, Christopher Singley wrote:
>
> On 5/30/19 10:23 PM, Christopher Lam wrote:
>> Not sure how it works internally.
>>
>> Perfect matches whereby fitid=online_id are hidden. I'd prefer not to hide,
>> but just grayed out... Because it's disconcerting downloading
Is it a good experience keeping GnuCash books in a SQL backend? There's
much better Python tooling if you can make the interface at SQL.
Looks like there's piecash, a SQLAlchemy frontend for GnuCash. This
looks promising. It's got good docs, too.
Is the piecash documentation correct that
On 5/30/19 10:23 PM, Christopher Lam wrote:
Not sure how it works internally.
Perfect matches whereby fitid=online_id are hidden. I'd prefer not to
hide, but just grayed out... Because it's disconcerting downloading an
ofx and find that the import list is very sparse.
Unmatched ofx txns
