Add PreparedStatement::get_arrow_schema (no execution) - #34
Merged
Merged
Conversation
C++ shim prepared_statement_get_arrow_schema in lbug_arrow namespace uses the new core PreparedStatement::getColumnNames/getColumnTypes (parse + bind + plan only) via ArrowConverter, mirroring query_result_get_arrow_schema. Requires LadybugDB core with lbug_prepared_statement_get_arrow_schema support.
adsharma
force-pushed
the
feat/prepared-statement-arrow-schema
branch
from
September 14, 2026 22:52
e590950 to
0f53959
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
C++ shim prepared_statement_get_arrow_schema (lbug_arrow namespace) derives the Arrow schema from the bound+planned statement via ArrowConverter, mirroring query_result_get_arrow_schema, plus cxx bridge entry and PreparedStatement::get_arrow_schema behind the arrow feature.
Depends on LadybugDB/ladybug#970 (needs core PreparedStatement::getColumnNames/getColumnTypes); CI here builds against a pinned core, so this should merge after the core PR lands in a consumed core version.
Consumer: ladybug-adbc-rs GetFlightInfo, so a Flight round trip executes the query exactly once (in DoGet). Untested end-to-end by design.