Open kudla opened 3 years ago
I'm also wondering how one configures what schema the migration tables are stored under. (I've got an automatic API generator and I'd like to keep the migrations tables out of where it's looking.)
It looks like this issue was reported back in 2017 (#459).
Same issue for me. Will this ever be tackled?
I'm submitting a...
Please how should one deal with the schemas?
Current behavior
Currently I define schema similar to how it is described in docs
Both migration table and migration content are created in the
public
schema.Behavior is the same regardless of the defined schema existence.
Expected behavior
Minimal reproduction of the problem with instructions
I've tried both
ENV
link and exact valueWhat is the motivation / use case for changing the behavior?
Using data separation on schemas level
Environment