Specify DB Schema for Collections When Table Already Exists #10970
brunowego
started this conversation in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm evaluating Payload as an "Internal Tool" and have set the default schema to payload. However, in my public schema, I already have existing tables that I’d like to use in collections. It would be great to specify the schema directly in the collection configuration, allowing Payload to work with existing tables without requiring migration or duplication.
This would improve integration with databases that already have a predefined structure. Is there currently a way to configure this? If not, are there any plans to support this functionality?
Beta Was this translation helpful? Give feedback.
All reactions