Update gnucash-sql section of README.
This commit is contained in:
parent
7becc4c0c5
commit
7325ff6187
1 changed files with 11 additions and 3 deletions
14
README.md
14
README.md
|
@ -153,10 +153,18 @@ pricehist fetch ecb EUR/AUD -s 2021-01-01 -o gnucash-sql | psql -U username -d d
|
||||||
|
|
||||||
Beware that the GnuCash project itself does not support integration at the
|
Beware that the GnuCash project itself does not support integration at the
|
||||||
database level, so there is a risk that the SQL generated by `pricehist` will
|
database level, so there is a risk that the SQL generated by `pricehist` will
|
||||||
be ineffective or even damaging for some version of GnuCash.
|
be ineffective or even damaging for some version of GnuCash. In practice, this
|
||||||
|
strategy has been used successfully by other projects. Reading the SQL and
|
||||||
|
keeping regular database backups is recommended.
|
||||||
|
|
||||||
In practice, this strategy has been used successfully by other projects.
|
The GnuCash database must already contain commodities with mnemonics matching
|
||||||
Reading the SQL and keeping regular database backups is recommended.
|
the base and quote of new prices, otherwise the SQL will fail without making
|
||||||
|
changes.
|
||||||
|
|
||||||
|
Each price entry is given a GUID based on its content (date, base, quote,
|
||||||
|
source, type and amount) and existing GUIDs are skipped in the final insert, so
|
||||||
|
you can apply identical or overlapping SQL files multiple times without
|
||||||
|
creating duplicate entries in the database.
|
||||||
|
|
||||||
### Show source information
|
### Show source information
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue