Add DB_SCHEMA support for PostgreSQL connections#2449
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe PostgreSQL schema can now be selected through the database settings command or ChangesDatabase configuration
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@config/database.php`:
- Line 104: Update the temporary PostgreSQL connection construction in
DatabaseSettingsCommand to use the configured DB_SCHEMA value, defaulting
consistently to public, instead of hardcoding search_path to public. Keep the
connection test aligned with the application's database configuration.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
I have read the CLA Document and I hereby sign the CLA |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
This PR adds support for configuring the PostgreSQL schema/search path through an environment variable.
Currently the PostgreSQL connection config uses a hardcoded
publicsearch path. This makes it difficult to run the panel in environments where a dedicated PostgreSQL schema is preferred instead of using the defaultpublicschema.Changes
DB_SCHEMAenvironment variable support for PostgreSQL connectionspublicas the default value to preserve current behaviorExample