<[EMAIL PROTECTED]>, users@appfuse.dev.java.net
Sent: Wednesday, October 10, 2007 2:12:17 PM (GMT-0800) America/Los_Angeles
Subject: Re: [appfuse-user] Data Archive pattern in AppFuse
Hi Nathan,
On 10 Oct 2007 at 12:42, Nathan Anderson wrote:
> We are currently not working with a hu
Hi Nathan,
On 10 Oct 2007 at 12:42, Nathan Anderson wrote:
> We are currently not working with a huge data set. The two tables we are
> auditing have 5,800 and 1,400 records. And the audit tables have 29,000 and
> 8,200 records.
Ah, but you have separate audit tables though, so operations on
Hi Nathan,
Thanks for your thoughts.
On 9 Oct 2007 at 11:25, Nathan Anderson wrote:
> We have an app that uses the Hibernate version attribute to make a "archive
> table" like you describe.
>
> Some things to think about before you get too far... The foreign key
> constraint means you will
Rob Hills" <[EMAIL PROTECTED]>
To: users@appfuse.dev.java.net
Sent: Sunday, October 7, 2007 10:25:40 PM (GMT-0800) America/Los_Angeles
Subject: [appfuse-user] Data Archive pattern in AppFuse
Hi All,
Sorry if this is a bit off topic, but in the app I am building, I need to
implement
a data archive
Hi All,
Sorry if this is a bit off topic, but in the app I am building, I need to
implement
a data archive pattern. IOW, in some tables, any changes to data (deletes,
updates) are preserved and made available to be reviewed in context (ie
from the UI for the table in question). So for exampl
