Dynamic Data Store Feature List in EPiServer CMS 6 Release Candidate
The EPiServer CMS 6 Release Candidate is quite near now so I wanted to list the features in the Dynamic Data Store that have made it this far.
Saving Data
+ Save compile-time typed data (normal .NET classes)
+ Save runtime typed data (using EPiServer.Data.Dynamic.PropertyBag class)
Loading Data
+ Load data as the Type is was saved as
+ Load data into a PropertyBag
+ Load data into a different .NET Type to the one that was saved
Finding & Searching Data
+ Simple Find using equality matching for one or more properties
+ LINQ support for more advances scenarios
POCO Support
+ Internally managed identity for object graph support
+ Stateful store instances for CRUD operations
+ Ability to provide identity separate from object when saving
Type to Store Mapping
+ Globally using EPiServer.Data.Dynamic.GlobalTypeToStoreMap
+ Globally using EPiServer.Data.Dynamic.EPiServerDataStoreAttribute
+ Locally using EPiServer.Data.Dynamic.TypeToStoreMapper delegate
Store to Custom Big Table Mapping
+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters
+ Using EPiServer.Data.Dynamic.EPiServerDataTableAttribute and EPiServer.Data.Dynamic.EPiServerDataColumnAttribute
Indexing of Properties
+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters
+ Using EPiServer.Data.Dynamic.EPiServerDataIndexAttribute
Custom Mapping of .NET Type
+ Using System.Runtime.Serialization.DataContractAttribute and DataMemberAttribute
+ Using EPiServer.Data.Dynamic.EPiServerDataContractAttribute and EPiServerDataMemberAttribute
+ Using EPiServer.Data.Dynamic.ITypeHandler
Store Re-mapping
+ Add new properties
+ Remove properties
+ Rename properties
+ Change data type of properties (where convertible)
Type Resolving
+ Automatic .NET Type resolving (e.g. when an assembly gets a new version number)
+ Programmer controlled .NET Type resolving via Assembly redirects
I aim to provide some simple How To’s for all of the features over the coming days and weeks.
Comments