migrator class doesn't allow specifying a schema to put migration tables

[DanielFGray]

It would be really nice if users could specify a schema to put the kysely_migration tables in (at least when using postgres I'm not sure how it would translate in other databases)

If this is already an existing feature I couldn't find it in the docs..

[koskimas]

So kysely should also create the schema right? Or can we expect it to exist?

[DanielFGray]

Great question. create schema if not exists would make sense to me, and I can't think of any reason why this wouldn't be desirable, except if you typo'd the schema name

[koskimas]

You can specify the schema like this

new Migrator({
  migrationTableSchema: 'some_schema'
})

in the next version.

[koskimas]

Released in 0.18.1

[Marko351]

Is there any implementation available for MSSQL?

[rafaelbsky]

I'm having an issue where, even though I did:

new Migrator({
  migrationTableSchema: 'my_schema'
})

it creates the 2 kysely tables (migrations and lock) in the correct schema I specified but still creates the migration tables in the public schema.

[koskimas]

@rafaelbsky that's what it's supposed to do. migrationTableSchema === "Schema for the migration tables". Not for your own tables.

You can bind your Kysely instance you give to Migrator to the schema using db.withSchema('my_schema') https://kysely-org.github.io/kysely-apidoc/classes/QueryCreator.html#withSchema