First class schema support through RIVER_SCHEMA and -schema - #629
Merged
Conversation
bgentry
approved these changes
Jul 31, 2026
Here, similar to what exists in the main River project, bring first class support for custom schemas to River UI (previously, it was necessary to work around non-support using `search_path`). Both `riverui` and `riverproui` start taking a schema via either the `RIVER_SCHEMA` env var or the `-schema` flag. Leaving these empty preserves the previous behavior in having River UI fall back to schemas enumerated in `search_path`. Fixes #628.
brandur
force-pushed
the
brandur-first-class-schema
branch
from
July 31, 2026 17:02
d3db009 to
0828442
Compare
Collaborator
Author
|
Thanks! Just a note I had to uncomment a replace in |
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
2 participants
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.
Here, similar to what exists in the main River project, bring first
class support for custom schemas to River UI (previously, it was
necessary to work around non-support using
search_path).Both
riveruiandriverprouistart taking a schema via either theRIVER_SCHEMAenv var or the-schemaflag. Leaving these emptypreserves the previous behavior in having River UI fall back to schemas
enumerated in
search_path.Fixes #628.