New Accounting Data Model for PG Backend

[Matthew Vanecek]

--=-PclHaXcf4EVCZspBtY+9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I've posted my data model for the Postgresql back end.  This model does
not include the business objects yet.  I'm also planning on including
Budgeting support, which should translate to the XML fairly easily.  If
there are any other data modeling masochists out there, I'd like some
feedback WRT the normalization and relationships.  I used the exciting
'new' UML to do this model, since that seems to be the wave of the
future...

I'm happy with the model, and really just want some other eyes to look
at it to make sure I didn't leave an entity or two out.

Also, suggestions about maintaining an audit trail would be
appreciated.  The current implementation duplicates the trailed tables'
structures into new tables + some extra columns (e.g., Account, and then
AccountTrail is just like Account but with some extra columns).  I don't
like all that duplication, but I'm having a hard time imagining an
effective and easy to maintain audit trail design. :(  Perhaps there
isn't one.=20

http://home1.gte.net/res0t4mo/projnotes/

Thanks,
--=20
Matthew Vanecek
perl -e 'print
$i=3Dpack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
***************************************************************************=
*****
For 93 million miles, there is nothing between the sun and my shadow
except me.
I'm always getting in the way of something...

--=-PclHaXcf4EVCZspBtY+9
Content-Type: application/DEFANGED-0; name="signature_asc.DEFANGED-0"

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

iD8DBQA9z0iuOMmiB1jXEBsRAhVtAJ9uLIP5w8S3mA9ZruqzljN9j1XdOACggtqr
tBa0L/QK2s20zswi+LKIWaI=
=07FD
-----END PGP SIGNATURE-----

--=-PclHaXcf4EVCZspBtY+9--