Change function does not exist

[MaxThom]

Describe the bug

When using the Change method, I get this error message from surrealdb: sending request failed for method 'change': Method not found I am using surreal version 1.3.1

I see the latest version of the code changed this method to Merge(), but it doesnt seem to be in the latest release. So I assume, my surrealdb version is to new for the last release?

Moreover, will the sdk transform any nil value to NONE so they get removed in surreal?

Thank you!

Steps to reproduce

Start the surrealdb v1.3.1 Call the Change() method from the sdk

Expected behaviour

To update my document

SurrealDB version

1.3.1 amd64

Contact Details

No response

Is there an existing issue for this?

• [X] I have searched the existing issues

Code of Conduct

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

[ElecTwix]

modify method has been changed to merge on upstream use lastest main commit. check out for more context: https://github.com/surrealdb/surrealdb.go/pull/98

[MaxThom]

Thanks!

[MaxThom]

I have notice the last release is more than a year old ? should there be a new release?

Moreover, I have now updated to follow main, and I can't access marshal and unmarshal function. I have to import the package "github.com/surrealdb/surrealdb.go/pkg/marshal"

Also, the Connect function requires a conn.Connection which is not specified in any of the doc. What should we provice?

I am running this version using got get ...@main github.com/surrealdb/surrealdb.go v0.2.2-0.20240612173039-8f4a6983912f I have updated my surreal to be 1.5.4.

Thanks

[Dash83UPV]

There is the same issue in "ws.py" with the function "merge" it says that the method 'change' does not exists.

[tobiemh]

Hi @MaxThom thanks so much for opening this issue 😃 👍. Since the date of this issue, the Golang SDK has seen significant changes, with support for both HTTP and WebSocket connections, full support of the SurrealDB RPC methods, a binary communication protocol using CBOR, and support for embedding SurrealDB in memory and with SurrealKV coming soon. As a result, I'm going to close this issue as this issue is no longer relevant in the latest code base 🚀 🎉.