Books/Accounting Periods proposal

[Linas Vepstas]

--uZ3hkaAS1mZxFaxD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 07, 2001 at 11:50:48AM -0400, Derek Atkins was heard to remark:
> I, too, like plan A.  However instead of thinking about files, I'd
> prefer if we did keep things in the abstract 'book'.  A book could be

Yes.  Although its kind of hacked up at the moment, and needs cleaning,=20
writing to a 'file' is just another 'backend'.  The splitting-up operation
I propose all happens above this interface.

(However, the naming convention for the different 'files' should be consist=
ent
with what different backends allow-- and I'm not clear on that ...)

> don't know, and you shouldn't care.  However, whatever we do should be
> something that is tied into the backend.  It would be nice if closing
> books might even be a backend function, rather than an engine
> function.  I'm not sure.

Good point.  I'd forgotten.  The sql backend might function more effiiecien=
tly if
things weren't split up. ...

--linas

--uZ3hkaAS1mZxFaxD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE60emDZKmaggEEWTMRAgwEAJ0VgzQipdI8VkVznbkHcJo8PP8amgCdG5TW
0E7MuFcasYeh+9uHHMvfyZE=
=PbTJ
-----END PGP SIGNATURE-----

--uZ3hkaAS1mZxFaxD--