Retrieve Schema from Backend to Fix Binary Data Issues #2938
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enhances the schema handling by retrieving schema information directly from the backend, rather than having the frontend infer it. Accurate schema retrieval is needed due to the binary data.
Previously, binary data was incorrectly treated as a string on the frontend, leading to issues differentiating between string and binary types. For instance, strings containing '0' and '1' were misinterpreted as binary data, resulting in byte representations being displayed in the result panel. This update ensures that the frontend receives the correct schema information, improving data type accuracy and presentation.
By aligning the schema across the backend and frontend, this change resolves existing issues and provides more reliable handling of binary data.