modifying data (e.g. updateTable) inside a migration about kysely HOT 5 CLOSED

This is now fixed in 0.27.2

from kysely.

The whole query builder is untyped in the migrations by design. Migrations must always be runnable and the code can never change, but the types change when the project evolves. If we used column types in the migration, what'd happen to your migration when, for example, the id field of your emails table is renamed to email_id?

from kysely.

Oh, it's actually any and not ExpressionBuilder<any>. Sorry about that. Yeah it should still be an ExpressionBuilder.

from kysely.

Makes sense, but couldn't the callback to (for example) the untyped .set((eb) => ...) get an instance of ExpressionBuilder<any> rather than just any?

from kysely.

For now you can use this

const eb = expressionBuilder<any, string>()
await db
  .updateTable('emails')
  .set({
    id: eb.ref('emails.id')
  })
  .where('id', 'is', null) // <-- null instead of 'NULL'

from kysely.