Geeks With Blogs

News kaleidoscope 1817, lit. "observer of beautiful forms," coined by its inventor, Sir David Brewster (1781-1868), from Gk. kalos "beautiful" + eidos "shape" (see -oid) + -scope, on model of telescope, etc. Figurative meaning "constantly changing pattern" is first attested 1819 in Lord Byron, whose publisher had sent him one.

Kaleidoscope Everything under the sun, ending in .Net

Below is the approach that can be implemented whenever there is a requirement of creating an Azure Table having entities with different schema definitions.


We can have a Parent Entity defined which will hold the data common in all the entity types and then rest all entities should inherit from this parent class.

There will be only on DataServiceContext class which will accept the object of the Parent class and this can be used for CRUD operations of all the entities.

Hope this approach helps!


Technorati Tags: ,
Posted on Wednesday, December 8, 2010 10:03 PM | Back to top

Comments on this post: Azure Table–Entities having different Schema (Implementation Approach)

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © kaleidoscope | Powered by: