Skip to content

PostgreSQL/JSONB backend #35

Open
Open

Description

@simontaurus

Add PostgreSQL/JSONB backend (extend SqliteDocumentStore pattern). Optimize query generation for nested JSON paths.

Acceptance Criteria

  • PostgreSQL/JSONB backend implementation
  • Follows SqliteDocumentStore pattern
  • Optimized query generation for nested JSON paths
  • Integration tests with PostgreSQL

Activity

  1. raederan commented on Nov 16, 2026

    @raederan
    Member

    Status of the acceptance criteria, and which PR covers what:

    Criterion State PR
    PostgreSQL/JSONB backend implementation done #180
    Follows the SqliteDocumentStore pattern done #180
    Integration tests with PostgreSQL done, CI runs PostgreSQL 16, 17 and 18 #180
    Optimized query generation for nested JSON paths done #181, stacked on #180

    How to proceed:

    1. Review and merge feat(backend): query nested JSON paths with a GIN index in PostgresDocumentStore #181 into ci-test-backends, the branch of feat(backend): add PostgresDocumentStore and test it on PostgreSQL 16-18 in CI #180.
    2. Merge feat(backend): add PostgresDocumentStore and test it on PostgreSQL 16-18 in CI #180 into main without squashing, so every commit reaches the changelog. feat(backend): add PostgresDocumentStore and test it on PostgreSQL 16-18 in CI #180 then carries both PRs.
    3. PostgreSQL/JSONB backend #35 closes with that merge, so feat(backend): add PostgresDocumentStore and test it on PostgreSQL 16-18 in CI #180's description changes from Refs #35 to Closes #35 once feat(backend): query nested JSON paths with a GIN index in PostgresDocumentStore #181 is in.

    Scope notes for the query part (#181):

    • Nested paths reach embedded objects only. A link is an IRI reference, so querying through a link raises.
    • The SPARQL resolvers reject nested paths (and |) instead of guessing.
    • Out of scope here: connection pooling, and range queries served by an index (only equality uses the GIN index).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

M2Core Features Complete

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions