Re: [PHP] Change tracking

Mike Smith wrote: Thanks Steven/Tony for your replies. I'll consider this a bit more before I jump in. I appreciate different perspectives. And I'll have to digest Tony's solution. Thanks, Mike Smith If you're on mysql you can combine the whole lot and speed up your db by adding in spatial in

Re: [PHP] Change tracking

Thanks Steven/Tony for your replies. I'll consider this a bit more before I jump in. I appreciate different perspectives. And I'll have to digest Tony's solution. Thanks, Mike Smith

Re: [PHP] 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

Re: [PHP] Change tracking

-- On Fri, 10/31/08, Mike Smith <[EMAIL PROTECTED]> wrote: > [INVENTORY_TABLE] > fieldsexample data > part 1027P > serial543221-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: Ano

[PHP] Change tracking

I'm about to try this, but I'd like some suggestions. I have a inventory table that an employee can update specific fields if they are incorrect, e.g. [INVENTORY_TABLE] fieldsexample data part 1027P serial543221-K qty 120 location G-5 I'd like to record what changed. Let's say