Why change-tracking has to be part of an entity object(weblogs.asp.net)

submitted by gosergoser(140) 5 years, 1 month ago

Frans Bouma raises some valid concerns on the Entity Frameworks entity state management.

1 comment |category: |Views: 19

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by jovovitchVer1jovovitchVer1(0) 5 years, 1 month ago 0

Well !! One of the overriding principles of object-oriented development is the proper assignment of responsibility in the given application.It means that the application must be capable enough to sense the changes either caused because of internal or external resources.
If we look into the observer pattern ..it catagorises the arcitecture into two --

A) Observer object
B) Subject object

Its a general convention that only those objserver can observe the Changes which are registered to accept the changes and modify the field based on the modification.

Reply

information Login or create an account to comment on this story