IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

smell check

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@4317 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Linas Vepstas 2001-05-28 04:40:14 +00:00
parent 5da31575ef
commit ef58540e6f
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/engine/sql/design.txt
View File

@ -22,13 +22,13 @@ indicates which mode the database is functioning.
This mode exists because it is easy to implement, easy
to debug, and has reasonable demands on the database for small
datasets. It is not efficeint for large datasets, and has
datasets. It is not efficient for large datasets, and has
a certain amount of risk in its use: because it erases the
old data before writing the new data, it is prone to any
problems during the 'save'. For example, if the database
crashes during the write (very unlikely), data could be lost.
If gnucash has some certain kind of bug (possible), not all
of the data may be saved. If gnucash crashes before a save,
If GnuCash has some certain kind of bug (possible), not all
of the data may be saved. If GnuCash crashes before a save,
then any changes since the last save would be lost.
This mode is mutually exclusive of any other access mode:
@ -76,7 +76,7 @@ If you want incremental deletion, then use the 'Single Update' mode.
Connecting to Postgres
----------------------
The postgres API requires a database to connect to. The initial
The Postgres API requires a database to connect to. The initial
connect is made using the "template1" database, which is the default
database that is always created when Postgres is installed. Thus,
we assume its always present.