Repository navigation
Add optional JSON queries and parameters for all three databases - #2
Merged
Merged
Conversation
added 5 commits
November 1, 2026 10:20
DoctorRemoteControl
added a commit
that referenced
this pull request
Nov 2, 2026
Add optional JSON queries and parameters for all three databases
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.
Database clients can now query rows as Jackson JSON nodes and bind JSON values through prepared statements using their existing PostgreSQL, SQLite, or DuckDB transaction connection.
Adds the optional
de.drremote.db:jsonbundle withJsonQueriesand immutableJsonValuesnapshots, plus the separatede.drremote-db-jsonKaraf feature. Existing database modules remain unchanged and require no Jackson dependencies. The caller retains connection and transaction ownership; statements and result sets close on success and failure.The adapter preserves JDBC numeric values, distinguishes SQL NULL from JSON null when binding, recognizes native JSON/JSONB, and supports explicit parsing of text columns. Coverage includes mixed SQLite runtime types, temporal/nested SQL arrays, binary values, invalid JSON trees, and resource cleanup. English documentation and a buildable OSGi JSON settings client show migrations, readiness, reads, and updates. CI builds both examples.
Validation: