Skip to content

Fix Adbc.Connection.query_pointer/5 warning when using adbc >= 0.9#1154

Open
nTraum wants to merge 1 commit into
elixir-explorer:mainfrom
hexafarms:adbc_deprecation
Open

Fix Adbc.Connection.query_pointer/5 warning when using adbc >= 0.9#1154
nTraum wants to merge 1 commit into
elixir-explorer:mainfrom
hexafarms:adbc_deprecation

Conversation

@nTraum
Copy link
Copy Markdown

@nTraum nTraum commented Jun 4, 2026

adbc 0.9 deprecated the 2-arity callback of Adbc.Connection.query_pointer.

When using explorer with adbc 0.9 or newer, this generates lots of deprecation warnings. This commit fixes it by using the newer 1-arity callback if available.

The docs of Adbc.StreamResult mention:

You must always hold a whole reference to the struct, and not individual fields. For example, if you only keep a reference to result.pointer, then the struct will be GCed, and so would be the stream.

I am unsure what to do with information and whether

Explorer.PolarsBackend.Native.df_from_arrow_stream_pointer(stream_result.pointer)

in the callback is enough to keep the reference alive long enough.

adbc 0.9 deprecated the 2-arity callback of `Adbc.Connection.query_pointer`.

When using explorer with adbc 0.9 or newer, this generates lots of deprecation warnings.
This commit fixes it by using the newer 1-arity callback if available.
@nTraum nTraum marked this pull request as ready for review June 4, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant