Tracking Data Changes (entities)

> I'm thinking of adding support to my entity classes to
track when values
> change similar to the dataset - i.e. when a property
changes I store the
> original value. I'm thinking that my base class will
have a accept/reject
> changes etc. Does anybody have any suggestions or
things not to do up front.
> Any papers blogs greatly appreciated.

I suggest that you take a long look at the awesome stuff
that Rockford
Lhotka has put together in his CSLA.Net library.  Full
source and a
very detailed book about the design philosophy and code are
available.
 It does EVERYTHING except the O/R Mapping to the database,
but
definately includes all the change-management, in-memory
rollback,
remoting and all that other cool stuff.

http://www.lhotka.net/
cslanet/

--
"We do not have the luxury of making that risky
assumption that people
will not be affected by the potential change. I know this
can be
frustrating for you as it is for us. Thanks for your
understanding in
this matter.." --Some misguided soul at Microsoft

Marc C. Brooks
http://musingmarc.blog
spot.com

===================================
This list is hosted by DevelopMentorŪ  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

+1,000




-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM]On Behalf Of Marc Brooks
Sent: Thursday, August 31, 2006 6:52 PM
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-CLR] Tracking Data Changes (entities)


> I'm thinking of adding support to my entity classes to
track when values
> change similar to the dataset - i.e. when a property
changes I store the
> original value. I'm thinking that my base class will
have a accept/reject
> changes etc. Does anybody have any suggestions or
things not to do up
front.
> Any papers blogs greatly appreciated.

I suggest that you take a long look at the awesome stuff
that Rockford
Lhotka has put together in his CSLA.Net library.  Full
source and a
very detailed book about the design philosophy and code are
available.
 It does EVERYTHING except the O/R Mapping to the database,
but
definately includes all the change-management, in-memory
rollback,
remoting and all that other cool stuff.

http://www.lhotka.net/
cslanet/

--
"We do not have the luxury of making that risky
assumption that people
will not be affected by the potential change. I know this
can be
frustrating for you as it is for us. Thanks for your
understanding in
this matter.." --Some misguided soul at Microsoft

Marc C. Brooks
http://musingmarc.blog
spot.com

===================================
This list is hosted by DevelopMentorŪ  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com


===================================
This list is hosted by DevelopMentorŪ  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

You may want to check out the
System.ComponentModel.IEditableObject
interface.

IEditableObject is what DataRowView uses to keep track of
old and new
values.

IEditableObject is a part of a family of interfaces that are
used to
implement data binding.  You dont have to implement all of
them.

The MSDN Docs for this interface does provide an example
implementation.


----- Original Message -----
From: "Phil Sayers" <philCDS-AM.NET>
To: <DOTNET-CLRDISCUSS.DEVELOP.COM>
Sent: Friday, September 01, 2006 07:57
Subject: Re: [DOTNET-CLR] Tracking Data Changes (entities)


> +1,000
>
> 
>
>
> -----Original Message-----
> From: Discussion of development on the .NET platform
using any managed
> language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM]On Behalf Of Marc Brooks
> Sent: Thursday, August 31, 2006 6:52 PM
> To: DOTNET-CLRDISCUSS.DEVELOP.COM
> Subject: Re: [DOTNET-CLR] Tracking Data Changes
(entities)
>
>
>> I'm thinking of adding support to my entity
classes to track when values
>> change similar to the dataset - i.e. when a
property changes I store the
>> original value. I'm thinking that my base class
will have a accept/reject
>> changes etc. Does anybody have any suggestions or
things not to do up
> front.
>> Any papers blogs greatly appreciated.
>
> I suggest that you take a long look at the awesome
stuff that Rockford
> Lhotka has put together in his CSLA.Net library.  Full
source and a
> very detailed book about the design philosophy and code
are available.
> It does EVERYTHING except the O/R Mapping to the
database, but
> definately includes all the change-management,
in-memory rollback,
> remoting and all that other cool stuff.
>
> http://www.lhotka.net/
cslanet/
>
> --
> "We do not have the luxury of making that risky
assumption that people
> will not be affected by the potential change. I know
this can be
> frustrating for you as it is for us. Thanks for your
understanding in
> this matter.." --Some misguided soul at Microsoft
>
> Marc C. Brooks
> http://musingmarc.blog
spot.com
>
> ===================================
> This list is hosted by DevelopMentorŪ  http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com

>
> ===================================
> This list is hosted by DevelopMentorŪ  http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com


===================================
This list is hosted by DevelopMentorŪ  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com