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
{{ message }}
Repository navigation
Dot notation write several levels deep into an Object field is handled inconsistently across adapters #10806
A dot notation write whose path descends through a stored value that is not a container (a scalar) inside an Object field is handled inconsistently across storage adapters, and PostgreSQL loses the original value.
Given a class with an Object field objectField storing { numberField: 5 }, an update with { "objectField.numberField.child": null } (i.e. writing child beneath the scalar numberField):
PostgreSQL: returns 200 and silently replaces the scalar, storing objectField = { numberField: { child: null } } — the original 5 is lost.
Create a class with an Object field, e.g. objectField.
Create an object: { "objectField": { "numberField": 5 } }.
Update it with a dot notation key descending through the scalar: { "objectField.numberField.child": null }.
Read the object back and compare across MongoDB and PostgreSQL.
Actual Outcome
PostgreSQL: objectField becomes { numberField: { child: null } } (the stored 5 is silently discarded).
MongoDB: HTTP 500; object unchanged.
Expected Outcome
Consistent, non-lossy behavior across adapters — either a clear client error (4xx) on both, or preservation of the existing value. A scalar intermediate value should not be silently replaced, and an invalid nested write should not surface as a 500.
Environment
Reproduced on current alpha (9.x) and release-8.x.x (8.x); not adapter-version specific.
Notes
Not security-sensitive: it only affects freeform nested data inside an Object field, for an object the caller can already write.
ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
Activity
parse-github-assistant commentedon Oct 19, 2026
🚀 Thanks for opening this issue!
ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.