Pomelo.EntityFrameworkCore.MySql

Pomelo.EntityFrameworkCore.MySql copied to clipboard

ICollection.Contains(...) on Json Column defined as a ICollection doesn't produce JSON_CONTAINS

5

Consider this entite: ```csharp public class House{ [Key] public int Id {get;set;} } public class Humans { [Key] public int Id {get;set;} [ColumnType(TypeName="json")] public List HouseIds {get;set;} = []; }...

idavidmarshali

See https://github.com/dotnet/efcore/issues/35361#issuecomment-2556914129 upstream. The fix is part of the EF Core 10 release train. The test should verify that #1776 has been fixed by EF Core upstream.

lauxjpn

[EFCore.Visualizer](https://marketplace.visualstudio.com/items?itemName=GiorgiDalakishvili.EFCoreVisualizer) now [supports MySQL](https://github.com/dotnet/efcore/issues/23125#issuecomment-2690791993). We should mention that in our docs, to aid users in debugging their queries.

lauxjpn

string.PadLeft and string.PadRight wrong translation

1

https://github.com/npgsql/efcore.pg/issues/3116 Please see above issue raised for Postgres; MySQL has the same issue where the implementations don't produce the same results in .NET vs MySQL. Many thanks

codemunkie15

MySQL/MariaDB perform a floating point division for operands of any type (which is not the .NET behavior), while different DBMS' (SQL Server, Sqlite, PostgreSQL) perform an integer division if both...

lauxjpn

EF.Functions.JsonExtract path parameter cannot contain variable

1

### Steps to reproduce This works: var c = dbContext.Set().OrderByDescending(o => EF.Functions.JsonExtract(o.Opportunity_Customfields, "$.field_2")).ToList(); But this throws an error: var path = $"$.{propertyName}"; var d = dbContext.Set().OrderByDescending(o => EF.Functions.JsonExtract(o.Opportunity_Customfields, path)).ToList(); Same...

wjadevries