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
As per my comment above, I think the issue is that in the sql files I'm not using the schema name prefixed to the table names and this is why it creates it in the public schema.
I think a "SET SCHEMA " should be issued before running the migrations to make sure any sql that's read is appended on the correct schema.
Expected Behavior
Schema
myschema
used for the creation of themigrations
tableMigrate Version
v3.4
Loaded Database Drivers
postgres, postgresql
The text was updated successfully, but these errors were encountered: