-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: modify RETURN value #150
Comments
Hello @J05HM0N5TER Well, this is an interesting idea. However, the core database does not support this behavior at the moment. If you want to see something like this, I suggest you to create an issue in this repository. Once this is implemented in the core database, we could then implement this behavior in every SurrealDB SDK including the .NET one. |
@Odonno I don't understand, what do you mean by it doesn't support it? Is this something to do with the cbor communication or something? I linked documentation on how to do it using surrealQL, and I have used if myself. |
The These methods only return the On the other hand, if you want this behavior right now, I suppose you can use the |
Is your feature request related to a problem?
When I use Upsert, Insert, or Update, I want to be able to change the return value to
NONE
for performance improvements. I am migrating a lot of data and producing the ID's before I create them in SurrealDB and store them in Valkey, which I found is faster for storing simple mappings between strings and IDs. When I write the SurrealQL directly, then I can specify this, and it seems to give better performance.Describe the solution
Provide an Enum for the return type as a parameter which has the options NONE, BEFORE, AFTER (the default). I am not sure if the others are practical when deserilising them into a C# object.
Alternative methods
Maybe have a separate function where it's called
InsertWithoutRespose
? I think this options is a lot worse than the primary solution idea.SurrealDB version
2.1.0 for linux on x86_64
Package version(s)
Contact Details
[email protected]
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: