JSON Documents API #39

c-nv-s · 2022-01-15T13:10:32Z

c-nv-s
Jan 15, 2022

https://github.com/tidwall/summitdb#json-documents

summitdb has a decent JSON Documents Redis-Style API.

could it be possible to implement something like this to have responses back as JSON

c-nv-s · 2022-01-15T13:19:59Z

c-nv-s
Jan 15, 2022
Author

also... I haven't pulled the v5 image to test it out yet but from the new README it looks like you have removed a lot of the old functionality.
does this mean there is no more:

SUBSCRIBE [<channel1> <channel2>], if there is no channel specified, it will be set to *
PUBLISH <channel> <payload>
WEBHOOKSET <channel> <httpurl>, register a http endpoint so it can be notified through JSON POST request with the channel updates, this command will return a re
8000
ference ID so you can manage it later.
WEBHOOKDEL <ID>, stops listening on a channel using the above reference ID.
WEBSOCKETOPEN <channel>, opens a websocket endpoint and returns its id, so you can receive updates through ws://server.address:port/stream/ws/{generated_id_here}
WEBSOCKETCLOSE <ID>, closes the specified websocket endpoint using the above generated id.

0 replies

alash3al · 2022-01-16T14:58:10Z

alash3al
Jan 16, 2022
Maintainer

Welcome, @c-nv-s ,

Regarding JSON support, I was thinking about something similar to the mentioned example, and for sure everything could be supported, but let's define some reliable use cases that use json specific commands, i.e, why don't we just use SET user:100 {JSON_PAYLOAD_HERE}?
Regarding the mentioned commands, yes I removed a lot of commands, but I plan to add them again but based on the new structure

3 replies

c-nv-s Jan 16, 2022
Author

i.e, why don't we just use SET user:100 {JSON_PAYLOAD_HERE}?

yes this is fine. but then when you want to change just one specific field in the json you have to copy the whole thing, edit it the resubmit it?
unless you allow for doing SET user:100 .contactDetails.email "mr@something.tld"
but I thought that is a different function signature so wouldn't be compatible with the typical Redis SET no?
whichever way you would do it, I think it would be a useful feature.

*yes I removed a lot of commands, but I plan to add them again but based on the new structure

awesome I'll look forward to when those commands return because they were awesome!

8000

c-nv-s Apr 2, 2023
Author

don't know how I've only just realized this, but this SET user:100 .contactDetails.email "mr@something.tld" is actually the function signature of HSET

c-nv-s Apr 3, 2023
Author

so you could actually use HSET to map to jsonb column in postgres and that would give much more control over the json that is returned or stored

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

JSON Documents API #39

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

JSON Documents API #39

Uh oh!

c-nv-s Jan 15, 2022

Replies: 2 comments · 3 replies

Uh oh!

c-nv-s Jan 15, 2022 Author

Uh oh!

alash3al Jan 16, 2022 Maintainer

Uh oh!

c-nv-s Jan 16, 2022 Author

Uh oh!

c-nv-s Apr 2, 2023 Author

Uh oh!

c-nv-s Apr 3, 2023 Author

c-nv-s
Jan 15, 2022

Replies: 2 comments 3 replies

c-nv-s
Jan 15, 2022
Author

alash3al
Jan 16, 2022
Maintainer

c-nv-s Jan 16, 2022
Author

c-nv-s Apr 2, 2023
Author

c-nv-s Apr 3, 2023
Author