Quoting Charles Day <[EMAIL PROTECTED]>:
> This may be a silly question, but why is GnuCash limited to using dates that
> are supported by time_t? Could we get rid of time_t?
>
> I don't need to enter 18th century transactions; I'm just curious.
time_t is #seconds since 1970-01-01 00:00:00
So yo
gnc-backend-dbi.c needs the tweak to stomp out GType warnings:
gnc-backend-dbi.c:948: warning: format ‘%d’ expects type ‘int’, but
argument 5 has type ‘GType’
gnc-backend-dbi.c:964: warning: format ‘%d’ expects type ‘int’, but
argument 5 has type ‘GType’
gnc-backend-dbi.c:980: warning: format
> Looking through the
> source code and the provided examples, it looks like the API can be used
> both for reading and writing. No help available anywhere on how to
> actually use that stuff?
Documentation is pretty bad right now. Help needed.
The examples you refer to are found in
gnucash/trun
This may be a silly question, but why is GnuCash limited to using dates that
are supported by time_t? Could we get rid of time_t?
I don't need to enter 18th century transactions; I'm just curious.
Cheers,
Charles
___
gnucash-devel mailing list
gnucash-d
As of rev 17323, the gda-dev2 backend supports mysql and postgresql databases
again. Despite the name, it uses the DBI library
(http://libdbi.sourceforge.net).
In the file menu, the 'Database Connection' menu entry allows you to save to or
load from one of these databases. This entry brings u
Thank you for adding it.
Now I am an AUTHOR of a scheme program :-)
Joachim
Charles Day schrieb:
>
>
> Yes, that fixed it. This patch looks good to me now, so I committed it
> as r17316 and requested backport. Joachim, I also added you to the
> AUTHORS file (hope you don't mind). Thank you
