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. http://home1.gte.net/res0t4mo/projnotes/ Thanks, -- Matthew Vanecek perl -e 'print $i=pack(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...
signature_asc_DEFANGED-0.DEFANGED-1800
Description: application/defanged-1800
