feat(sdk): add Context.withSchema schema-scoped contexts - #77
Closed
damusix wants to merge 10 commits into
Closed
Conversation
Collaborator
Author
|
Redundant — this change reaches master via the v1.1.0 promotion PR #76. |
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.
Summary
ctx.withSchema<SDB, SProcs, SFuncs, STvfs>(name)derives a schema-scopedContextsharing the parent's connection, pool, and lifecycle — the query builder,proc/func/tvf, transactions, and impersonation all resolve against the schema, with fresh generics typing the schema's slice. Re-deriving replaces rather than stacks; dotted routine names keep the caller's qualification; rawsqlfragments stay untouched by design.@noormdev/sdkminor changeset and documentation across the SDK README, API reference, and dev guide.Same change previously merged to
nextvia #75; this is the rebase ontomaster.What this solves
Multi-schema users had to hand-qualify every query and routine call; one missed call site silently targeted the default schema.