Anders Hattestad
Jan 12, 2011
(4 votes)

Dynamic Data Store and new properties on Types

When you use access the data store you get your object with the properties from the first time you created the store. If you have added properties on thje type the definition in the store is not updated, and your object will be missing values from the new properties.

That's a bit hassle, since I guess most of you will add new properties after the first time the store is created.

So instead of accessing the store like this

Code Snippet
  1. public static DynamicDataStore Store
  2. {
  3.     get
  4.     {
  5.         return DynamicDataStoreFactory.Instance.GetStore(typeof(ProductItem)) ??
  6.                DynamicDataStoreFactory.Instance.CreateStore(typeof(ProductItem));
  7.     }
  8. }
I have created myself and extension method so
Code Snippet
  1. public static DynamicDataStore Store
  2. {
  3.     get
  4.     {
  5.         return DynamicDataStoreFactory.Instance.GetCreateEnsureStore(typeof(ProductItem));
  6.     }
  7. }

Where the actually code is like this.

Code Snippet
  1. using System;
  2. using System.Collections.Generic;
  3. using System.Linq;
  4. using System.Web;
  6. namespace EPiServer.Data.Dynamic
  7. {
  8.     public static class StoreExtensions
  9.     {
  10.         static object lockObject = new object();
  11.         static Dictionary<Type, bool> done = new Dictionary<Type, bool>();
  12.         public static DynamicDataStore GetCreateEnsureStore(this DynamicDataStoreFactory factory,Type type)
  13.         {
  14.             bool isFirstTime = true;
  15.             lock (lockObject)
  16.                 if (!done.TryGetValue(type, out isFirstTime))
  17.                     isFirstTime = true;
  18.             if (isFirstTime)
  19.             {
  20.                 var result= factory.GetStore(type);
  21.                 if (result == null)
  22.                     result = factory.CreateStore(type);
  23.                 else
  24.                 {
  25.                     var def = result.StoreDefinition;
  26.                     def.Remap(type);
  27.                     def.CommitChanges();
  28.                 }
  29.                 lock (lockObject)
  30.                 {
  31.                     done[type] = false;
  32.                 }
  34.             }
  35.             return factory.GetStore(type);
  36.         }
  38.     }
  39. }

This code will on the first time it get accessed, checks if the store exits, and if not creates it. And if it exists, it will be remap to the type before it returns the store.

Jan 12, 2011


Erik Nordin Wahlberg
Erik Nordin Wahlberg Jan 12, 2011 09:25 PM

Nice one, was wondering how to solve this the other day. :)

Anders Hattestad
Anders Hattestad Jan 12, 2011 10:51 PM

My previous method was to delete the store and create a new one...
So it’s a big improvement :)

Jan 13, 2011 09:19 AM

Interesting code, but I can't figure out why you use the lockObject? Is it only to make it thread safe or what is its purpose?

Anders Hattestad
Anders Hattestad Jan 13, 2011 10:20 AM

Just to make it thread safe,
I thought that could be a good idea, but I quess most of the times this isn't a problem.
I lock when I do a read, but are not sure if that's necessery. Did google it, and was some contradiction statements about it Jan 13, 2011 03:29 PM

You can also check if the store actually needs remapping like this:

var def = result.StoreDefinition;
if (!def.ValidateAgainstMappings(typeof(type), false))

Anders Hattestad
Anders Hattestad Jan 13, 2011 05:39 PM

That was a good tip. It felt wrong to always remap the store, but I didn't bother to look further.

Anders Hattestad
Anders Hattestad Jan 13, 2011 06:00 PM

Have added Mr Smith's code and uploaded it here

Joshua Folkerts
Joshua Folkerts Jan 31, 2011 02:43 PM

Very nice. I was trying to do this, this weekend. Thanks for the generosity.

Please login to comment.
Latest blogs
Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog