docs(web): expand database module page (docs-03)#134
Merged
Conversation
…itOps Problem-first rewrite covering custom endpoint comparison operators (including CONTAIN), introspection as Admin API-only, and state export resources.
✅ Deploy Preview for mystifying-borg-373afd canceled.
|
❌ Deploy Preview for trusting-goodall-362511 failed.
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
conduit-web | 266d110 | Commit Preview URL Branch Preview URL |
Jun 22 2026, 11:24 AM |
Document $ilike support on PostgreSQL and clarify that operation 8 currently falls through to equality, not array-contains.
3 tasks
This was referenced Jun 22, 2026
Use full prose instead of prose-sm, restore td align-top, improve blockquote and heading rhythm, and fix layout in deep-dive fragments.
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.
What kind of change does this PR introduce?
Docs-03: problem-first rewrite of the database module page from
Conduit/modules/databasesource.Does this PR introduce a breaking change?
The PR fulfills these requirements:
mainbranchSummary
Developers often hit the same wall:
GET /database/{Schema}returns an unfiltered collection, so filtering in app code leaks data and skips authorization. This PR reframes the database module page around that problem, then documents the correct patterns.conduitOptions(CMS, authz, permissions), extensionsscopeon creates, populate/sort/pagination0–8(including CONTAIN for array fields), assignment actions,likesearch caveatsmcp: false(not available as MCP tools)schemas,extensions,customEndpointsexport priorities and link to the GitOps guideTest plan
/docs/modules/databaseOther information:
Sourced from
Conduit/modules/database(handlers, admin routes,Database.tsexport resources). No application code changes.