You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please check if your Feature Request has not been already raised in the Discussions Tab, as we would like to reduce duplicates. If it has been already raised, simply upvote it 🔼.
Is your proposal related to a problem?
Jackson doesn't support using a postgres schema other than 'public'. In a large enterprise projects using the npm package, depending on your architecture, using public can be undesirable due to things like database roles/permissions, existing migrations, etc.
Describe the solution you'd like
Jackson should support specifying a postgres schema.
Describe alternatives you've considered
Use a distinct user for jackson and execute ALTER USER <user_name> SET search_path TO <schema>;. This can work but it would be cleaner and safer to have native support.
The text was updated successfully, but these errors were encountered:
Fixesboxyhq#1818.
This commit adds postgres schema support to the app logic.
The dev environment uses synchronize function to create tables,
and does not run the explicit migrations. We will add schema support
for production in the next commit.
Fixesboxyhq#1818.
This commit adds postgres schema support to the app logic.
The dev environment uses synchronize function to create tables,
and does not run the explicit migrations. We will add schema support
for production in the next commit.
Is your proposal related to a problem?
Jackson doesn't support using a postgres schema other than 'public'. In a large enterprise projects using the npm package, depending on your architecture, using public can be undesirable due to things like database roles/permissions, existing migrations, etc.
Describe the solution you'd like
Jackson should support specifying a postgres schema.
Describe alternatives you've considered
Use a distinct user for jackson and execute
ALTER USER <user_name> SET search_path TO <schema>;
. This can work but it would be cleaner and safer to have native support.The text was updated successfully, but these errors were encountered: