You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The type hierarchy support provided by Marten is great, I use it to build hierarchies based on interfaces (as I use F# where inheritance is not idiomatic).
For planning purposes, I am wondering if Marten provides a way to safely refactor my code - typically by moving classes to a different namespace - without losing the ability to deserialize existing records.
My understanding is that Marten relies on the mt_dotnet_type_column to deserialize interfaces so I gather that I'll be screwed the minute the fully qualified name of my concrete types change 😆
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
The type hierarchy support provided by Marten is great, I use it to build hierarchies based on interfaces (as I use F# where inheritance is not idiomatic).
For planning purposes, I am wondering if Marten provides a way to safely refactor my code - typically by moving classes to a different namespace - without losing the ability to deserialize existing records.
My understanding is that Marten relies on the
mt_dotnet_type_column
to deserialize interfaces so I gather that I'll be screwed the minute the fully qualified name of my concrete types change 😆Beta Was this translation helpful? Give feedback.
All reactions