We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://supabase.com/docs/guides/realtime/postgres-changes
The realtime client is decoding data from JSON (no support for binary data), how is the binary data encoded?
What about all other values like dates, big ints, etc?
Describe how the serialization is done, even better if you switch to a binary format for encoding data, something like msgpack maybe
msgpack
From what I can see it is encoded to a string that looks like the following:
\x30343036663238326632666330663030383739656463663365313.....
It looks like it's base 10 encoded https://hexdocs.pm/phoenix/Phoenix.Socket.Serializer.html
The text was updated successfully, but these errors were encountered:
abytes
No branches or pull requests
Improve documentation
Link
https://supabase.com/docs/guides/realtime/postgres-changes
Describe the problem
The realtime client is decoding data from JSON (no support for binary data), how is the binary data encoded?
What about all other values like dates, big ints, etc?
Describe the improvement
Describe how the serialization is done, even better if you switch to a binary format for encoding data, something like
msgpack
maybeAdditional context
From what I can see it is encoded to a string that looks like the following:
It looks like it's base 10 encoded
https://hexdocs.pm/phoenix/Phoenix.Socket.Serializer.html
The text was updated successfully, but these errors were encountered: