Json support for primitive array types - no contraint json_valid added

[meriturva]

We are migrating from the Pomelo to the Microting provider. Leveraging the native JSON support introduced in recent EF Core versions, we want to move some configurations from custom ValueConverters/validators to direct EF Core management

For example configuration for Roles (string[]) from:

builder.Property(cce => cce.Roles)
  .HasColumnName("Roles")
  .HasColumnType("json")
  .HasConversion(
          v => JsonSerializer.Serialize(v, _jsonSerializerOptions),
          v => JsonSerializer.Deserialize<string[]>(v, _jsonSerializerOptions)
      );

become simply:

builder.Property(cce => cce.Roles)
  .HasColumnName("Roles");

While this simplifies our codebase significantly, it introduces a consistency gap: the database lacks a native constraint to validate the JSON format (e.g., json_valid(Roles)). Consequently, while the mapping works perfectly, we currently need to add these validation checks manually at the DB level.

Any advice?
So thanks.
Diego

[renemadsen]

@meriturva since we don't use json in any of our production code, I cannot give you any advice on to what is best to do.

If you can come up with what the MySQL/MariaDB correct query would be, then we can look into it, but if it's not something that can be done in the engines, there is nothing I'm willing to do, since then it would be custome to solve a problem the underlying DB engine is not able to solve for us.

Hope that helps. I'll keep the issue open, but it will be closed at some point if nothing new is getting posted to help understand what maybe needs to be done.