Change Tracking Proxies

Nov 21, 2012 at 9:12 PM

Am I correct in thinking that NO uses Entity Framework Change Tracking Proxies?

Refer: http://blog.oneunicorn.com/2011/12/05/should-you-use-entity-framework-change-tracking-proxies/

Editor
Nov 21, 2012 at 9:16 PM
yup. That's why you have to write:

persist(ref myEntity)

... the original entity gets replaced with a proxy


On 21 November 2012 22:12, jfbosch <notifications@codeplex.com> wrote:

From: jfbosch

Am I correct in thinking that NO uses Entity Framework Change Tracking Proxies?

Refer: http://blog.oneunicorn.com/2011/12/05/should-you-use-entity-framework-change-tracking-proxies/

Read the full discussion online.

To add a post to this discussion, reply to this email (nakedobjects@discussions.codeplex.com)

To start a new discussion for this project, email nakedobjects@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Nov 22, 2012 at 6:07 AM
Tnx.
Was just confirming it was those kind of proxies. :)
Editor
Nov 22, 2012 at 7:10 AM
If I'm wrong, I guess Stef will jump in...

Coordinator
Nov 22, 2012 at 11:03 AM

That is correct.  Incidentally, that's why Naked Objects requires that all properties are virtual  -  so the proxy can override them.

Nov 22, 2012 at 11:45 AM
Ok, thank you.
Will you get some kind of error if a property is not virtual? Or will it just not be overridden?
Coordinator
Nov 22, 2012 at 1:12 PM

By default NakedObjects will throw an error if properties are not virtual - this behaviour can be overrided by setting the 'EnforceProxies' flag on the EntityPersistorInstaller to false.

 

 

 

 

Nov 22, 2012 at 3:50 PM
Perfect. Tnx