Open
Description
I trying to get db-migrate to create the migration table in a schema of my choosing, to no avail. After a brief look through the code, it seems to me that the schema attribute in database.json is never used. If I understand the code correctly, the config object is passed directly to the node-postgres driver, which does nothing with the schema attribute.
This issue here is possibly relevant, it basically states that schema specification through config is not supported.
Am I missing something?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Activity
pedro-ribeiro commentedon Apr 5, 2017
Same problem here.
wzrdtales commentedon Apr 9, 2017
@pedro-ribeiro @stefaneg Ok, seems like this needs a bit of hoop jumping to make it work with pg. Thanks for reporting!
LiamKarlMitchell commentedon Nov 3, 2017
Could we have a post connect query executed for set options?
Other database/scenarios may also benefit from running some set options to configure the session some way before any other sql commands are executed.
(ANSI NULLS SQL server etc if someone ever made a connector for that)
Example:
Providing the user/role has the appropriate grants on that schema?
Note: Ended up just making multiple users with different configured search paths to work around this.
oaltman commentedon Apr 4, 2018
any update on this?
Koofii commentedon Nov 14, 2018
Any update on this?
davetheninja commentedon Oct 4, 2019
All can someone confirm if this was ever fixed?
I am using the latest beta and am getting the same issue.
If it has been fixed and it’s now a regression can someone tell me which version to roll back to please.
kylecombes commentedon Sep 22, 2021
I'm still seeing this problem.
nstylo commentedon Dec 21, 2023
Still seeing this issue. Not sure if this ever will be fixed.