Re: Change tracking

I've always used a version field (just an incrementing id) rather than an effective date field. I can see the benefits of being able to look back and see when the changes were made and if done correctly make it so things don't change until a certain date. Hmmm nifty. Stephen wrote: > -- On Fri, 10/31/08, Mike Smith <mikeosmith@gmail.com> wrote: > > >> [INVENTORY_TABLE] >> fields example data >> part 1027P >> serial 543221-K >> qty 120 >> location G-5 >> >> I'd like to record what changed. Let's say they >> change the serial. One way >> would be a "static" changes table: >> > > Another way is to never change a record, but to add new ones. You also need to add an > effectivity date field. > > Stephen > >