Errors when entity has a JSONB column - postgres - naming convention not respected

[ocoster-sermo]

I have an entity with a JSONB column - when trying to bulk update (either in an object graph using IncludeGraph = true or with multiple bulk inserts using a transaction), I am getting errors.

The naming convention I use is snake case, meaning a property Promotions should be translated to promotions and IsTrue to is_true. This works for all other columns in my entity, except for this JSONB type (configured in mapping to use ToJson).

I am getting errors like the following:

C#

PostgresException: 42703: column "Promotions" of relation "employeeTempaa5d0fea" does not exist

DB logs:

    ERROR:  column "Promotions" of relation "employeeTempaa5d0fea" does not exist
    STATEMENT:  COPY "public"."employeeTempaa5d0fea" ("id", "building_id", "created_at", "eligible_for_bonus", "location_id", "manager_id", "modified_at", "original_building_id", "provider_id", "provider_settings_id", "status", "Promotions") FROM STDIN (FORMAT BINARY);
    ERROR:  current transaction is aborted, commands ignored until end of transaction block
    STATEMENT:  DROP TABLE IF EXISTS "public"."employeeTempaa5d0fea"
    LOG:  could not receive data from client: An existing connection was forcibly closed by the remote host.  

Here's a sample repo showing the issue (see Tester.cs - and a script to create the DB tables in the root folder).

[ocoster-sermo]

I've been testing more and even in cases where I am doing a simple bulk insert I will get errors (from memory, something to the tune of having data for 4 columns, when there are 5 - which is correct when you don't consider the id column that is an autoincrement and that is decorated with the KeyAttribute, so should not be considered anyway).

[charlespamart]

Any news on this issue ?

I have the exact same problem

[pdouelle]

I'm also encountering this issue with JSONB columns in PostgreSQL
Looking forward to a fix
Thanks

[Pepouzz]

I have the same issue
hope it will be fixed soon
Thank you