You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are lots of reasons why someone would want to serialize a query response:
Saving to disk. We do this on the docs team.
Message-passing situations (e.g., web workers, or webviews in VS Code).
Fetching query results on the backend and forwarding the results to the frontend.
Currently, response objects that include Arrow relations do not survive serialization and deserialization via JSON. Instead, one needs to use tableToIPC/tableFromIPC to serialize/deserialize arrow relations and also MetadataInfo.fromJsonString/MetadataInfo.fromJson to serialize/deserialize metadata. This isn't all that hard to do, but it is pretty hard to figure out, and it would be reasonable for those methods to be provided by the SDK.
For inspiration, here's what we do in the VS Code extension:
There are lots of reasons why someone would want to serialize a query response:
Currently, response objects that include Arrow relations do not survive serialization and deserialization via JSON. Instead, one needs to use
tableToIPC/tableFromIPC
to serialize/deserialize arrow relations and alsoMetadataInfo.fromJsonString/MetadataInfo.fromJson
to serialize/deserialize metadata. This isn't all that hard to do, but it is pretty hard to figure out, and it would be reasonable for those methods to be provided by the SDK.For inspiration, here's what we do in the VS Code extension:
The text was updated successfully, but these errors were encountered: