Skip to content

fix(pgsql): opt into Npgsql dynamic JSON so ProfileData reads work again — PRODUCTION OUTAGE #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MusaMisto merged 1 commit into from
Sep 1, 2026
Merged

fix(pgsql): opt into Npgsql dynamic JSON so ProfileData reads work again — PRODUCTION OUTAGE #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion SW.Mtm.Web/Startup.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Microsoft.IdentityModel.Tokens;
using Npgsql;
using Pomelo.EntityFrameworkCore.MySql.Infrastructure;
using Pomelo.EntityFrameworkCore.MySql.Storage;
using SW.CqApi;
Expand Down Expand Up @@ -51,11 +52,27 @@ public void ConfigureServices(IServiceCollection services)

if (mtmOptions.DatabaseType.ToLower() == RelationalDbType.PgSql.ToString().ToLower())
{
// Npgsql 8 removed the implicit dynamic JSON serializer. Properties
// mapped with StoreAsJson() (Tenant.ProfileData,
// TenantMembership.ProfileData, Account.ProfileData) are POCO
// collections stored in json/jsonb columns, and reading them now
// throws unless dynamic JSON is opted into explicitly:
// InvalidCastException: Reading as
// 'IEnumerable<ProfileDataItem>' is not supported for fields
// having DataTypeName 'jsonb'
// Built ONCE here, not inside the AddDbContext lambda:
// NpgsqlDataSource owns the connection pool, so building one per
// DbContext instance would leak pools.
var pgDataSourceBuilder = new NpgsqlDataSourceBuilder(
Configuration.GetConnectionString(MtmDbContext.ConnectionString));
pgDataSourceBuilder.EnableDynamicJson();
var pgDataSource = pgDataSourceBuilder.Build();

services.AddDbContext<MtmDbContext, PgSql.MtmDbContext>(c =>
{
c.EnableSensitiveDataLogging(true);
c.UseSnakeCaseNamingConvention();
c.UseNpgsql(Configuration.GetConnectionString(MtmDbContext.ConnectionString), b =>
c.UseNpgsql(pgDataSource, b =>
{
b.MigrationsHistoryTable("_ef_migrations_history", PgSql.MtmDbContext.Schema);
b.MigrationsAssembly(typeof(PgSql.DbType).Assembly.FullName);
Expand Down
Loading