Allow to ignore unsupported connection options#250
Merged
staticlibs merged 1 commit intoduckdb:mainfrom Jun 4, 2025
Merged
Conversation
Currently driver performs strict checks on the user-specified connection options. If stray options are passed - exception is thrown on connect. This is considered to be a good feature, to prevent accidental typos in option names. But in some cases user does not have full control over the options passed to driver by other tools. This change adds new boolean connection property `jdbc_ignore_unsupported_options`, when it is enabled - all unsupported connection options are ignored. When used with external tools, it is intended to be set in connection string like this: ``` jdbc:duckdb:;jdbc_ignore_unsupported_options=true; ``` Testing: new test added. Fixes: duckdb#232
2ea59fe to
b6cc97c
Compare
staticlibs
added a commit
to staticlibs/duckdb-java
that referenced
this pull request
Jun 6, 2025
This change restores the contents of duckdb#250 that were inadvertently removed in duckdb#247.
staticlibs
added a commit
to staticlibs/duckdb-java
that referenced
this pull request
Jun 6, 2025
This change restores the contents of duckdb#250 that were inadvertently removed in duckdb#247.
staticlibs
added a commit
to staticlibs/duckdb-java
that referenced
this pull request
Jun 16, 2025
This is a backport of the PR duckdb#250 to `v1.3-ossivalis` stable branch. Currently driver performs strict checks on the user-specified connection options. If stray options are passed - exception is thrown on connect. This is considered to be a good feature, to prevent accidental typos in option names. But in some cases user does not have full control over the options passed to driver by other tools. This change adds new boolean connection property `jdbc_ignore_unsupported_options`, when it is enabled - all unsupported connection options are ignored. When used with external tools, it is intended to be set in connection string like this: ``` jdbc:duckdb:;jdbc_ignore_unsupported_options=true; ``` Testing: new test added. Fixes: duckdb#232
staticlibs
added a commit
that referenced
this pull request
Jun 16, 2025
This is a backport of the PR #250 to `v1.3-ossivalis` stable branch. Currently driver performs strict checks on the user-specified connection options. If stray options are passed - exception is thrown on connect. This is considered to be a good feature, to prevent accidental typos in option names. But in some cases user does not have full control over the options passed to driver by other tools. This change adds new boolean connection property `jdbc_ignore_unsupported_options`, when it is enabled - all unsupported connection options are ignored. When used with external tools, it is intended to be set in connection string like this: ``` jdbc:duckdb:;jdbc_ignore_unsupported_options=true; ``` Testing: new test added. Fixes: #232
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
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.
Currently driver performs strict checks on the user-specified connection options. If stray options are passed - exception is thrown on connect.
This is considered to be a good feature, to prevent accidental typos in option names. But in some cases user does not have full control over the options passed to driver by other tools.
This change adds new boolean connection property
jdbc_ignore_unsupported_options, when it is enabled - all unsupported connection options are ignored.When used with external tools, it is intended to be set in connection string like this:
Testing: new test added.
Fixes: #232