Evengard
Evengard
Either I'm doing something incorrectly, or it doesn't help. The repro with the suggested code throws the same exception: Repro ```csharp using LinqToDB.Common; using LinqToDB.Data; using LinqToDB.EntityFrameworkCore; using LinqToDB.Mapping; using...
I've actually tried that too, but the result was the same. Reference: Repro ```csharp using LinqToDB.Common; using LinqToDB.Data; using LinqToDB.EntityFrameworkCore; using LinqToDB.Mapping; using LinqToDB.SqlQuery; using Microsoft.EntityFrameworkCore; using Microsoft.Extensions.Logging; using NodaTime;...
`timestamp without time zone` screenshot ![изображение](https://user-images.githubusercontent.com/798735/133662436-279ab9bd-8646-431a-810c-b3486b9f4fb7.png)
Well, using just `ms.SetConverter(timeStamp => timeStamp.ToDateTimeUtc());` kind of worked, with one problem. Npgsql with EF Core sets Kind.Undefined for such DateTime's, but this sets Kind.Utc. I can see how to...
Is there a way to set theese mapping schemas per DbContext? Sure, I can do ctx.CreateLinqToDBConnection and set the mappings on it, but will it apply to indirect calls such...
Another related problem, except this one seems to be more tricky. Consider a model like that: ```csharp public class Profile { [Key] public Guid Id {get; set;} [Column(TypeName = "jsonb")]...
I've managed to work it around with smth like this in my dbcontext: ```csharp this.CreateLinqToDbConnection().MappingSchema.SetConverter(json => JsonSerializer.Deserialize(json)); ``` but is there a way to pull that automatically, like EF Core...
Is there actually a way to assign a specific mappingcontext for a specific EF dbcontext? I really don't want to pollute the global default mappingschema with bindings specific to this...
I've managed to work it around for now with smth crazy like that: ```csharp private static void SetJsonConverter() { MappingSchema.Default.SetConverter((s) => JsonSerializer.Deserialize(s)); } static DbCtx() { var method = typeof(DbCtx).GetMethod(nameof(SetJsonConverter),...
Any progress on this one? My project heavily relies on some i386 C code (which we attempt to migrate to Go - but there's just too much, the process is...