You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #837, after upgrading Marten I'm getting the following error message when updating a type with a duplicated column:
schema "public" does not exist
I can see a statement being executed like:
update myschema.mt_doc_mytype as d set message_timestamp = public.mt_immutable_timestamptz(data -> 'Message' ->> 'Timestamp') where (d.tenant_id = :tenantid and d.id = :arg9)
^ Note the public.mt_immutable_timestamptz - also note that when creating my document store I am setting DatabaseSchemaName = myschema.
The problem seems to be here in DuplicatedField - a new, default StoreOptions is being created, instead of using the configured one.
The text was updated successfully, but these errors were encountered:
* fix: #1378, use configured StoreOptions
* Add back the original ctor, so no breaking change
* Revert laziness
* Add tests for #1378 fix
* Reverted change to test connection string
* Updated obsolete DuplicatedField constructor to use new one
* Formatting
Similar to #837, after upgrading Marten I'm getting the following error message when updating a type with a duplicated column:
schema "public" does not exist
I can see a statement being executed like:
update myschema.mt_doc_mytype as d set message_timestamp = public.mt_immutable_timestamptz(data -> 'Message' ->> 'Timestamp') where (d.tenant_id = :tenantid and d.id = :arg9)
^ Note the
public.mt_immutable_timestamptz
- also note that when creating my document store I am settingDatabaseSchemaName = myschema
.The problem seems to be here in DuplicatedField - a new, default
StoreOptions
is being created, instead of using the configured one.The text was updated successfully, but these errors were encountered: