Databases
StackOverflow2013
Postsdbo
POEF4 POCO: Snapshot vs Self-tracking over WCF
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEF4 POCO: Snapshot vs Self-tracking over WCF
    primarykey
    data
    text
    <p>Last year I developed a data access service for our project using Entity Framework (.NET3.5 of course) and using Julie Lerhman's book as a guide developed state tracking POCO objects. We use WCF and also have Silverlight 3 clients. We are moving to .NET 4.0 and I want to switch to using code generation to eliminate wasted developer time writing the POCO classes and the translation classes.</p> <p>With the research I have done there seems to be 3 ways of state tracking POCOs:</p> <p>1) Changed tracked proxies: Doesn't seem to be useful for us as it seems this doesn't work over WCF serialisation.</p> <p>2) Snapshot based: Snapshot is taken when POCO entity graph is retrieved, returned graph from client is compared with that snapshot and differences are compared...seems good to me.</p> <p>3) Self-Tracking Entities: Code generator generates logic for doing self tracking within the POCO objects. This seems close to what we do now except it is all generated for us.</p> <p>I am trying to work out what the advantages and disadvantages are between all of these methods. I am guessing that 1 and 2 are "connected" and that they need the ObjectContext that the POCOs were originally queried from to remain instanciated, but haven't been able to confirm this. I also don't see a reason why anyone would really bother with option 1 given that option 3 seems to do the same and more...</p> <p>Snapshot seems the simplest to me, but if this requires an ObjectContext to remain open for a long time I am not so sure...</p> <p>I am only a junior programmer so any advice here, especially with regards to Silverlight 3 (I believe options 2 and 3 work with Silverlight 3 but 2 may have issues) is much appreciated.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMrLane
    1. USMrLane
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEF4 POCO: Snapshot vs Self-tracking over WCF
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEF4 POCO: Snapshot vs Self-tracking over WCF
      1. USMrLane
      1. VTFavorite
    3. VO
      singulars
      1. POEF4 POCO: Snapshot vs Self-tracking over WCF
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAs an update, I am now using State Tracked Entities in our WCF/Silverlight 4 application and they work pretty well (though having issues with deletes). Navigation Properties are TrackableCollections now which derive from ObservableCollection so binding to XAML in a dream. I reccomend this solution very much.
      singulars
      1. POEF4 POCO: Snapshot vs Self-tracking over WCF
      1. USMrLane
    2. COPossible duplicate of http://stackoverflow.com/questions/3814706/self-tracking-entities-vs-poco-entities and of http://stackoverflow.com/questions/6116002/entity-framework-self-tracking-entities-vs-poco
      singulars
      1. POEF4 POCO: Snapshot vs Self-tracking over WCF
      1. USDanny Varod
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload