fix: Saving object with a pointer field set to `undefined` throws error for Postgres

[andrewalc]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #9146

Approach

Work in progress, attempting to write a failing test case. Need to see if it fails for Postgres in CI (afaik i can only test on mongo locally. It passes for mongo but shouldn't for postgres)

Tasks

• [ ] Add tests
• [ ] Add changes to documentation (guides, repository pages, code comments)
• [ ] Add security check
• [ ] Add new Parse Error codes to Parse JS SDK

[parse-github-assistant[bot]]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant[bot]]

Thanks for opening this pull request!

[mtrezza]

Test passes for Postgres and MongoDB. Is this issue related to your custom code?

[andrewalc]

Test passes for Postgres and MongoDB. Is this issue related to your custom code?

I just found out how to test with postgres locally so I'm gonna try setting that up properly first. My issue might be because I didn't configure postgres for parse correctly.

[mtrezza]

@andrewalc sure, let us know how it goes, and whether the related issue can be closed.

[andrewalc]

@andrewalc sure, let us know how it goes, and whether the related issue can be closed.

posted an update in the issue here, might try again if i find some time but it seems like the case i have refuses to fail in this repo