Deserialization order of jsonb about efcore.pg

[roji]

This is a PostgreSQL question about jsonb - Npgsql doesn't really play any role here.

The PG docs clearly state that:

Because the json type stores an exact copy of the input text, it will preserve semantically-insignificant white space between tokens, as well as the order of keys within JSON objects. Also, if a JSON object within the value contains the same key more than once, all the key/value pairs are kept. (The processing functions consider the last value as the operative one.) By contrast, jsonb does not preserve white space, does not preserve the order of object keys, and does not keep duplicate object keys. If duplicate keys are specified in the input, only the last value is kept.

So moving to jsonb would solve your issue (but would take away the advantages of jsonb). Another option would be to preprocess the json coming back from the database and rearrange it to have $type appear first, before passing it along for deserialization.

[mariotoffia]

Thanks for your prompt answer!

Cheers,
Mario