-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Derek Atkins schrieb: > Marcus, > > Marcus Wolschon <mar...@wolschon.biz> writes: > >> There must be a way without violating 1st normal form and storing >> everything twice. >> Maybe an "updated"-timstamp or something may help. > > Maybe... I was thinking about ways to avoid using timestamps per se,
Timestamps are created by the database-server and the database-server alone. (the SQL-function is called "now()") >> (Also I`m concerned that still loading all transactions from the db >> into ram will work >> out after a few years of bookkeeping. You cannot split a database by >> year as you can >> an xml-file. > > Why can't you? Because you would need to new databases with user access-rights and backup and everything. It`s not as trivial as copying a local file if the servers in the company are properly managed. Marcus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqJinIACgkQf1hPnk3Z0cRcOwCgn9UrMS/64nUdFW1/x9ECqUsr viAAnRyhr/4sIfitadlNrByXl9+jCNu2 =1FIV -----END PGP SIGNATURE----- _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
