Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Postgres: Schema does not default to current schema for references when Pt. 2
See original GitHub issueWhat are you doing?
I need to switch schemas dynamically for multi tenancy in an application and when I change the schema for a model, I would like sequalize to default to that schema for transitive gets. This is not the case yet and I would consider this a bug as it’s the only sensible default behaviour.
The main point where this happens is when I call model.schema('ZZZ').getXXX.
What do you expect to happen?
Sequalize to default to the schema ZZZ also for the related resource.
What is actually happening?
It defaults to no (public) schema.
Environment
Dialect:
- mysql
- postgres
- sqlite
- mssql
- any Dialect library version: XXX Database version: XXX Sequelize version: XXX Node Version: XXX OS: XXX If TypeScript related: TypeScript version: XXX Tested with latest release:
- No
- Yes, specify that version:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
let me rebase and update the PR first
Next try here: https://github.com/sequelize/sequelize/pull/13136
@papb please check and merge this time.