History of changed rows

------=_Part_1655_26061686.1208508746278
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 other idea?
Thanks
CPK

--
Keep your Environment clean and green.

------=_Part_1655_26061686.1208508746278--

Re: History of changed rows

--------------080900080907040804050706
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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 other idea?
> Thanks
> CPK
>
How about mysqlbinlog? :)


--------------080900080907040804050706
Content-Type: text/plain; charset=us-ascii


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
--------------080900080907040804050706--

Re: History of changed rows

--------------040503050505000004060506
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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 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 other idea?
> Thanks
> CPK
>
>
> ------------------------------------------------------------ ------------
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.519 / Virus Database: 269.23.1/1385 - Release Date: 4/18/2008 9:30 AM
>

--------------040503050505000004060506--

Re: History of changed rows

------=_Part_363_5958666.1208541217226
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Apr 18, 2008 at 8:13 AM, Peter Brawley
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 convention and it works well.

I have a real problem with how it suggests using NULL. NULL is undefined,
and they are basically abusing it to mean infinite positive. NULL has issues
being indexed, big datetime values don't.

At the recent postgres convention I eavesdropped on a discussion about a
possible new temporal range format which would basically consist of a start
date and an end date and preclude any other entries from overlapping. Such
a format would be ideal for PITA, but the start and end would need to be not
null...

--
Rob Wultsch
wultsch@gmail.com
wultsch (aim)

------=_Part_363_5958666.1208541217226--

Re: History of changed rows

------=_Part_6412_2067932.1208703734419
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks for all of you. I will test the suggestions and then reply.
CPK


--
Keep your Environment clean and green.

------=_Part_6412_2067932.1208703734419--