feat: Add exposed-postgres module with hstore support - #2912
Open
Matthew de Detrich (mdedetrich) wants to merge 1 commit into
Open
Matthew de Detrich (mdedetrich) wants to merge 1 commit into
Matthew de Detrich (mdedetrich) wants to merge 1 commit into
Conversation
Matthew de Detrich (mdedetrich)
force-pushed
the
add-exposed-postgres-with-initial-hstore-implementation
branch
from
September 5, 2026 09:24
dd2c61e to
e08c853
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
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.
Description
This PR adds the
exposed-postgresmodule which initially contains the hstore implementation, both theMap<String, String?>column type mappings and the dsl for both jdbc and r2dbc.Detailed description:
exposed-postgreshas been made containing the hstore extension. This was intentional and the reasoning behind it is that no other major DB vendor has a map like type (in other words hstore is unique to postgres). Initially when working on it I called the moduleexposed-postgres-hstorebut upon reflection using this strategy would have created an explosion in modules as its implying that each unique feature for each database needs its own module (where as withexposed-postgres, all of the postgres unique database features can be contained there)exposed-postgres), the actual implementation and DSL was largely based off of the existing postgres-json support. Unlike postgres-json, we didn't use a lowest common denominator of functions that are common with all DB vendors but instead provided full hstore functionality.On a related note, since we have now a module that is specific for postgres it also opens the capability of filling in gaps where current dsl's only implement lowest common denominator functionality for features that are common amongst all supported database vendors. As an example, currently the exposed-json doesn't support all of postgres's json/jsonb functionality because its not available in other databases, but with a
exposed-postgresmodule you can place those missing functions there i.e. here are the concrete gaps in Postgres's jsonb surface that exposed-json skips (Postgres-only, no MySQL/H2/SQLite/Oracle/SQLServer equivalent):||concat,-/#-delete-by-path (mirrors exactly what we just built for hstore)jsonb_set(),jsonb_insert()— targeted mutation by path@?/@@jsonpath match operators,jsonb_path_query()family (SQL/JSON path language, Postgres-specific implementation)#>/#>>path-extraction operators (distinct from the->/->>exposed-json already covers generically)Type of Change
Please mark the relevant options with an "X":
Updates/remove existing public API methods:
Affected databases:
Checklist