Re: [PHP] Change tracking
- From: sstelfox@xxxxxxx (Sam Stelfox)
- Date: Fri, 31 Oct 2008 15:12:50 -0400
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@xxxxxxxxx> 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
.
- Follow-Ups:
- Re: [PHP] Change tracking
- From: "Mike Smith"
- Re: [PHP] Change tracking
- References:
- Re: [PHP] Change tracking
- From: Stephen
- Re: [PHP] Change tracking
- Prev by Date: Re: Change tracking
- Next by Date: Re: [PHP] Change tracking
- Previous by thread: Re: [PHP] Change tracking
- Next by thread: Re: [PHP] Change tracking
- Index(es):