elwinar
No schema selected?
I have a bevy of migrations that are failing to run, due to the following error:
info initializing database
unable to initialize database: pq: no schema has been selected to create in
RAMBLER_SCHEMA is set to a schema that gets created inside of the migrations.
Unfortunately, the project is closed source or else I would share a link here, but is there a way to log additional debug?
Rambler version: 5.3.0
The issue is that rambler is trying to create a table at the initialization step to keep track of what migrations are applied, and can't do it because your schema doesn't exists yet. This is a chicken-egg issue that I don't have a clever solution for, as I don't use Postgres myself.
I'm open to suggestions tho, what would be correct behavior in this case given Postgres best-practices? Maybe we should force the migration table to be created in the public schema?
