Implement complex types (value objects)

[eveneveneven]

Greetings, this is a question/feature request:

Per the Limitations section of the Value Conversions documentation: "There is currently no way to spread a conversion of one property to multiple columns or vice-versa."

Is something like this planned, or is there an alternative better way to do this?
I'm looking for a way to keep the backing fields out of my entity classes. And to not use strings in the configuration or public backing fields in my entity classes.

Here's a quick example from my current code working with a legacy DB:

From an entity class:

      private DateTime _lastChanged { get; set; }
      private int _lastChangedHour { get; set; }
      private int _lastChangedMinute { get; set; }      
      public DateTime LastChanged
      {
         get
         {
            if (_lastChanged.Hour != 0 || 
                _lastChanged.Minute != 0 || 
                _lastChanged.Second != 0)
               return _lastChanged;

            var returnDateTime = 
               new DateTime(
                  _lastChanged.Year, 
                  _lastChanged.Month, 
                  _lastChanged.Day, 
                  _lastChangedHour, 
                  _lastChangedMinute, 
                  0);
            return returnDateTime;
         }

         set
         {
            _lastChangedHour = value.Hour;
            _lastChangedMinute = value.Minute;
            _lastChanged = value;
         }
      }

From the entity's configuration:

            builder.Ignore(o => o.LastChanged);

            builder
               .Property<DateTime>("_lastChanged")
               .HasColumnName("SIST_ENDRET")
               .HasColumnType("datetime")
               .HasDefaultValue((DateTime) SqlDateTime.MinValue);

            builder
               .Property<int>("_lastChangedHour")
               .HasColumnName("SIST_ENDRET_TIM")
               .HasColumnType("decimal(2,0)")
               .HasConversion<decimal>();

            builder
               .Property<int>("_lastChangedMinute")
               .HasColumnName("SIST_ENDRET_MIN")
               .HasColumnType("decimal(2,0)")
               .HasConversion<decimal>();

Thanks for your time!

[ajcvickers]

@divega to look for dupe.

[divega]

This issue could be considered a duplicate of #9906 "Use C# structs or classes as value objects", based on the triage notes at #9906 (comment), and the fact that #13067 was previously closed in favor of #9906.

But I personally don't think the association is clear, especially given that we don't have a design for #9906. I would prefer to keep this issue open to represent the desire to have value conversions that spread over multiple columns, so that customers can vote for it and discuss it independently of structs and value objects.

[mcd8604]

Having value conversions spread over multiple columns is exactly what I was hoping I could do. I have a property type (Length) in my data model which is defined as a struct in a third party library. It contains two critical data fields - the value (double) and the unit (enum). I simply want to map the value to a double column and the string-converted-enum to another column.

As a workaround, I ended up going with the same approach as the original poster. It is undesirable since it muddies up the data model:

Entity configuration in DbContext via Fluent API:

EntityTypeBuilder<PhysicalBraid> physicalBraidBuilder = modelBuilder.Entity<PhysicalBraid>();
physicalBraidBuilder.Property(p => p.Notes).HasColumnType("xml").HasConversion(v => XamlWriter.Save(v), v => XamlReader.Parse(v) as FlowDocument);
physicalBraidBuilder.Property<double>("measuredLength_Value");
physicalBraidBuilder.Property<LengthUnit>("measuredLength_Unit").HasConversion(new EnumToStringConverter<LengthUnit>());

Entity definition in Data Model:

public class PhysicalBraid : INotifyPropertyChanged {
	public int Id { get; set; }
	[Required]
	public virtual BraidDesign Design { get; set; }
	[Required]
	public virtual TurntableConfiguration StartConfiguration { get; set; }
	public virtual ObservableCollection<PhysicalBraidState> States { get; set; } = new ObservableCollection<PhysicalBraidState>();
	[NotMapped]
	public Length MeasuredLength {
		get => new Length(measuredLength_Value, measuredLength_Unit);
		set { measuredLength_Value = value.Value; measuredLength_Unit = value.Unit; }
	}
	private double measuredLength_Value { get; set; }
	private LengthUnit measuredLength_Unit { get; set; }
	public FlowDocument Notes { get; set; }

	public event PropertyChangedEventHandler PropertyChanged;
}

[ajcvickers]

Notes from planning: we decided to close this in favor of #9906 (Use C# structs or classes as value objects) or vice versa, but reading again the comment from @divega above, I think it does make sense to keep this as separate issues. However, we'll likely work on them together.

[NichUK]

+1 please...
I have a custom value type for some finance work, which I'd like to be able to store in a readable fashion, but right now my only option seems to be storing as a byte array. It works, but it's not what I'd like. Flattening my type into 3 columns in the main table would be perfect.