Skip to content

Archive/pr 2 before official identity 2026 07 20 - #6

Closed
Robbyfuu wants to merge 7 commits into
TabularisDB:mainfrom
Robbyfuu:archive/pr-2-before-official-identity-2026-07-20
Closed

Archive/pr 2 before official identity 2026 07 20#6
Robbyfuu wants to merge 7 commits into
TabularisDB:mainfrom
Robbyfuu:archive/pr-2-before-official-identity-2026-07-20

Conversation

@Robbyfuu

@Robbyfuu Robbyfuu commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Robbyfuu and others added 7 commits July 13, 2026 19:09
The Tabularis host is gaining URI passthrough for plugin drivers
(TabularisDB/tabularis#495): a driver that declares `connection_uri`
receives the raw connection string verbatim on `ConnectionParams`
instead of decomposed host/port fields, with the string stored in the
OS keychain on the host side.

Declare the capability plus the `mongodb` and `mongodb+srv` schemes.
`build_uri` already prioritizes `connection_uri` over decomposed
fields, so no runtime change is needed; a test now pins that exact
key as the wire contract.

`connection_string_example` is deliberately left out: on hosts
without the passthrough feature, an example would register the
`mongodb+srv` protocol and the URI would parse but be decomposed,
silently persisting a connection that fails at DNS resolution.
Omitting it keeps those hosts at the current loud validation error,
while hosts with passthrough register the schemes from
`connection_uri_schemes` directly.
The mongodb-atlas id collides with existing MongoDB plugin naming in
the ecosystem. The new id describes the actual differentiator —
connecting with a full connection URI — rather than a vendor. Bump to
0.2.0 since the id change means existing installs must reinstall under
the new directory.
Multi-database drivers receive 'database' as an array from the host,
and the strict string check rejected it with "Parameter 'database'
must be a string" before the connection URI was even used. Accept
string, array (first entry wins), or null in both the request handler
and the decomposed-URI builder.
Multi-database navigation sends the selected database in the request's
'schema' field; the plugin only ever looked at the connection-level
database, so every request was served from the first stored database
and collections came back with schema: null, which the host could not
associate with the database the user expanded. The request-level value
now outranks the connection default, and collection listings echo the
database they belong to.
The host quotes table names when it builds browsing queries
(SELECT * FROM "plans"), and the quotes were kept as part of the
collection name, so every table view queried a nonexistent collection
and came back empty.
@Robbyfuu

Robbyfuu commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator Author

Closing as superseded by #2. The current main branch already contains the Atlas/full-URI support, and subsequent #3/#4 changes migrated the plugin contract to .tabularium. Rebasing this archival branch would reintroduce the retired manifest.json/release identity. There are no unresolved review threads or failed checks on this PR; preserving the archive branch unchanged.

@Robbyfuu Robbyfuu closed this Aug 4, 2026
@Robbyfuu
Robbyfuu deleted the archive/pr-2-before-official-identity-2026-07-20 branch August 4, 2026 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant