Add PostgreSQL schema configuration support via DATABASE_SCHEMA #4681
Conversation
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
…onment variable This update enables users to specify a custom PostgreSQL schema for Flowise to use, improving database organization and multi-tenant deployments. Changes: - Add schema property to PostgreSQL DataSource configuration using DATABASE_SCHEMA env var - Configure search_path to include custom schema, public, and extensions schemas - Ensure UUID functions remain accessible from extensions schema - Maintain backward compatibility with default 'public' schema when DATABASE_SCHEMA is not set 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
just curious, under what scenario and condition that you might want to use other schema other than public, and searchPath too? can you give me an example? |
|
When you have more than one app in the same database and you want to maintain logical separation.
From: Henry Heng ***@***.***>
Date: Thursday, 3 July 2025 at 6:07 am
To: FlowiseAI/Flowise ***@***.***>
Cc: Stuart Hirst ***@***.***>, Author ***@***.***>
Subject: Re: [FlowiseAI/Flowise] Add PostgreSQL schema configuration support via DATABASE_SCHEMA (PR #4681)
[https://avatars.githubusercontent.com/u/26460777?s=20&v=4]HenryHengZJ left a comment (FlowiseAI/Flowise#4681)<#4681 (comment)>
just curious, under what scenario and condition that you might want to use other schema other than public, and searchPath too? can you give me an example?
—
Reply to this email directly, view it on GitHub<#4681 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJ4HB4N3MNMDYMOVI4EH33L3GQ3WDAVCNFSM6AAAAAB7UGO7QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMRZGE3TAMRSGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
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.
This update enables users to specify a custom PostgreSQL schema for Flowise to use, improving database organization and multi-tenant deployments.
Changes: