Thanks for all of you. I will test the suggestions and then reply.
CPK
--
Keep your Environment clean and green.
On Fri, Apr 18, 2008 at 8:13 AM, Peter Brawley <[EMAIL PROTECTED]>
wrote:
> CK,
>
> > How can we manage the history of changed rows in the database.
> >
>
> Point-in-time architecture. For a bit of discussion see
> http://www.artfulsoftware.com/infotree/tip.php?id=547
>
> PB
I have used this con
CK,
How can we manage the history of changed rows in the database.
Point-in-time architecture. For a bit of discussion see
http://www.artfulsoftware.com/infotree/tip.php?id=547
PB
-
C K wrote:
Hi all.
How can we manage the history of changed rows in the database. I have some
idea but
C K wrote:
Hi all.
How can we manage the history of changed rows in the database. I have some
idea but not yet implemented. By using triggers to make a copy of the row
being changed to the another table in the same db. Is there any way to only
save the changed fields data and field name? Any othe
No problem.
I do this using three triggers on Insert, Update and Delete. Then
update a log file who's schema starts:
CREATE TABLE ?_log (
id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
transact ENUM ('I','U','D') NOT NULL,
key_from_table ??? NOT NULL,
KEY (key_from_table),
field_1 ?? ,
