Well u don't want to slow down the db by keep all the old data in there, which will have to be searched through in your queries. So prob best to copy out the data to another table or even another DB when it is changed.
-----Original Message----- From: Phill B [mailto:[EMAIL PROTECTED] Sent: 11 May 2006 17:42 To: CF-Talk Subject: Re: Anyone done this before? That would have been a better way of putting it. Yes We want to track the changes made in the database. We would like to keep it indefinitely. On 5/11/06, Ben Nadel <[EMAIL PROTECTED]> wrote: > By auditing, do you mean tracking changes? If so, how long do you need > to keep the old data for? > > ....................... > Ben Nadel > Web Developer > Nylon Technology > 350 7th Avenue > Floor 10 > New York, NY 10001 > 212.691.1134 > 212.691.3477 fax > www.nylontechnology.com > > "You know, like nunchuck skills, bowhunting skills, computer hacking > skills... Girls only want boyfriends who have great skills." > - Napoleon Dynamite > -----Original Message----- > From: Phill B [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 11, 2006 11:12 AM > To: CF-Talk > Subject: Anyone done this before? > > We want to start auditing the database changes made in our home grown > CMS app. Anyone on here done this or have suggestions on where to > start with some thing like this? > > -- > Phil > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240238 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
