Return value after Set command

[XanderD99]

Add an optional flag to the set and fset commands that returns the full updated object in the response.

This would be a quality-of-life improvement that eliminates the need for an additional get call after each set/fset when the caller needs the complete object state. Returning the full object directly would reduce extra round-trip, simplify client logic, and improve overall efficiency, especially in workflows that immediately depend on the updated data.

[tidwall]

I can see the advantages. How do you envision the command looking?

[XanderD99]

Since we have EX, XX, and NX already for other things, I suggest adding RX, which is widely used in networking as receive. In this case, it would be to indicate to the SET and FSET that you want to receive the object in the body.

To perhaps further extend this feature could add RX to simply return the geometry, and RX WITHFIELDS to also include the fields. Just like the GET command.

[XanderD99]

To go into more detail and to follow the full GET parameters the option would look like this:

SET key id [FIELD name value ...] [EX seconds] [NX|XX|RX [WITHFIELDS] [OBJECT|POINT|BOUNDS|(HASH geohash)]] (OBJECT geojson)|(POINT lat lon z)|(BOUNDS minlat minlon maxlat maxlon)|(HASH geohash)|(STRING value)

Then the same for FSET

Edit: I have a working fork of this, which I am currently using

[gmonk]

Sorry to interject but would this be like an ACK to verify the set was successful if so this would be a nice feature.

[XanderD99]

I suppose you could use it to verify the object you want to set is actually the object that is returned.

My use case was more that I have 2 separated streams 1 that does a set and 1 that does an fset, those fan-in to single state stream and I didn't want to always have to call GET after the set/fset 😆