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

updates

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@4822 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Linas Vepstas 2001-06-27 06:44:40 +00:00
parent 46e97be3eb
commit c5ae7808e7
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/engine/sql/README
View File

@ -224,9 +224,6 @@ access).
-- Wire in the GUI to ask user for username/password to log onto the -- Wire in the GUI to ask user for username/password to log onto the
server. (GUI already implemented, just not yet used). server. (GUI already implemented, just not yet used).
-- change code for initial db access. We should query the pg_database
table to see if the database already exists.
-- distinguish between 'save' and 'save-as' in gnc-book & backend. -- distinguish between 'save' and 'save-as' in gnc-book & backend.
If user hits 'save' in the single-user or multi-user mode, it If user hits 'save' in the single-user or multi-user mode, it
should be a no-op (since the saves have already occured). Only should be a no-op (since the saves have already occured). Only
@ -269,11 +266,6 @@ access).
there will be other debilitating conditions if the backend disappears, there will be other debilitating conditions if the backend disappears,
leaving the engine in a possibly confused state. leaving the engine in a possibly confused state.
For example, if postgres user is misconfigured, the LOCK TABLE
will fail on session validate, and FINISH_QUERY will close the
connection. Subsequent sql will core dump gnucash, even though this
is a sysadmin error.
-- during open of register window, a query of splits is typically run -- during open of register window, a query of splits is typically run
twice (once during open -- LedgerDisplayInternal(), and again twice (once during open -- LedgerDisplayInternal(), and again
during LedgerDisplayRefresh()) this results in twice as much data during LedgerDisplayRefresh()) this results in twice as much data