"auto"-updates in store oncreate, onchange

[MatsJakobsson]

Hi!

We would love to have a property LastUpdatedDate being set on the entity on every Create and Update configured directly in the store.

Down the road, this type of configuration capability would also be helpful if we were to implement soft deletes etc.

Is this possible today without wrapping the store?

Many thanks for all the great work on the client!

[Elfocrash]

Hey @MatsJakobsson,

I don't know if I want to add such a feature for multiple reasons.

• CosmosDB already has this property in the form of the _ts field. Ofc this property is second precise and not millisecond which means that ordering won't be 100% accurate but with Indexing v2 being out now it should be fine for soft deletes.
• You can use a CosmosDB trigger to add or update those fields on the server side. Not saying this is a good idea, I'm just saying you can.
• Ideally the store should be wrapped in some form of repository or data context for multiple reasons, such as making extension methods unit testable or restricting the context to a specific job (ex, UserRepository using the TokenStore and the UserStore).

The way I see it, I wouldn't want to add something like that at this point unless there is a more general need for it. I think, it should be fine for the client side to set those value before add/update. I know it sucks to wrap the store if you didn't do it already but maybe it's the best solution at least for now.

I might, however, consider adding an action delegate that can mutate the document right before the action.

Does this make sense?

Thanks, Nick

[MatsJakobsson]

Hi Nick!

Thank you for you reply.

An action delegate with the possibility to mutate the document before the action would be really nice.

/Mats