Bug: upsert function does not work if one of the fields is readonly, even if it is not mentioned

[Nipodemos]

Describe the bug

When you try to use upsert, and the record already exists, and the record has a field that is readonly, it'll show the following error:

ResponseError: There was a problem with the database: Found changed value for field `updatedAt`, with record `test:nipo`, but field is readonly
      at new SurrealDbError (:1:33)
      at new ResponseError (C:\Users\Alan\Projetos Web\bugreportsurrealdbjs\node_modules\surrealdb\dist\index.mjs:1:4603)
      at C:\Users\Alan\Projetos Web\bugreportsurrealdbjs\node_modules\surrealdb\dist\index.mjs:1:49206

Steps to reproduce

i've created a repo with a minimal reproducible code: Link to repo

but the steps are:

1. create a table that has at least one readonly field
2. create a record, it must exist to error to appear
3. try use upsert on that existing record

Expected behaviour

to update only the fields i've mentioned on upsert function

SurrealDB version

2.0.2 for windows on x86_64

JavaScript SDK version

1.0.6

Contact Details

[email protected]

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[LucyEgan]

Sounds like its related to surrealdb/surrealdb#4952, does it work as expected against surrealdb 2.0.0-beta.2?

[Nipodemos]

I'll check tonight