defaultValueSql parameter is null but computedColumnSql is used instead

[gmartinezsan]

When overriding the ColumnDefinition method for the MySQL provider implementation the defaultValueSql parameter is always null even though the usage of the HasDefaultValueSql. Which seems to me that it should be assigned in the defaultValueSql parameter. Apparently the usage of ValueGeneratedOnAddOrUpdate in OnModelCreating method is causing that the value always is assigned to the computedColumnSql parameter.

how to reproduce it

Define an entity with the HasDefaultValueSql method. For example

  modelBuilder.Entity<Employee>()
         .Property(p => p.Timestamp)
         .HasDefaultValueSql("CURRENT_TIMESTAMP")
         .ValueGeneratedOnAddOrUpdate();

The table create script created does not include the current_timestamp default value on this column.

We also need to have a way to specify that the value only should be generated in the Update. Is there any way to specify it already?

Could you please give any guidance or explain if this working as expected?

Thanks in advance!

[rowanmiller]

Hey,

We are planning to change this. Currently HasDefaultValueSql + ValueGeneratedOnAddOrUpdate is interpreted to mean "computed column"... but this is not desirable so #4501 is tracking changing this behavior.

~Rowan

[gmartinezsan]

Thanks for clarifying. I will track that one for the updates.

[rowanmiller]

Sounds good, I'll close this one out.