From ef58540e6f4ea27be7f093e0607b039e5641260d Mon Sep 17 00:00:00 2001 From: Linas Vepstas Date: Mon, 28 May 2001 04:40:14 +0000 Subject: [PATCH] smell check git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@4317 57a11ea4-9604-0410-9ed3-97b8803252fd --- src/engine/sql/design.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/engine/sql/design.txt b/src/engine/sql/design.txt index 2037443641..1c7a8a3e0f 100644 --- a/src/engine/sql/design.txt +++ b/src/engine/sql/design.txt @@ -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.