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.
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.