kysely

• Fixes #135. Thank you @68kHeart ❤️

• Fixes #132

• Fix corner case bugs in withSchema
• Make postgres cursor compatible with pg-cursor typings

Breaking changes

The internal "operation node tree" changed a little bit. This only affects you if you've implemented a custom plugin or are doing something funky with the node tree. The only change is the new node SchemableIdentifier that's used by TableNode and a small set of other nodes that can have a schema.

• Fixes #131
• Exports WithSchemaPlugin

• Adds support for explaining queries. Thank you @igalklebanov
• Adds modifyFront and modifyEnd methods to the CreateTableBuilder. Thank you @igalklebanov
• Fixes #125. Thank you @igalklebanov
• Fixes #129

Fixes a potential security issue #121. Thank you @DavesBorges ❤️

• Adds query streaming. Thank you @elderapo ❤️
• Adds the replaceInto method. Thank you @igalklebanov ❤️

Added createType and dropType methods to the schema builder.

Added modifyFront and modifyEnd methods

Fix bug where falsy default values didn't set the hasDefaultValue value to true in ColumnMetadata.

Fixes #108

Added isAutoIncrementing and hasDefaultValue to ColumnMetadata.

Add support for lateral joins

const query = ctx.db
  .selectFrom('person')
  .innerJoinLateral(
    (eb) =>
      eb.selectFrom('pet')
        .select('name')
        .whereRef('pet.owner_id', '=', 'person.id')
        .as('p'),
    (join) => join.on(sql`true`)
  )
  .select(['first_name', 'p.name'])
  .orderBy('first_name')

Fix join method issues that caused typescript to fail with Type instantiation is excessively deep and possibly infinite.ts(2589)-

• Enables tree shaking for webpack
• Disables a webpack warning about a dynamic import in FileMigrationProvider
• Support .mjs files in migrations

Fixes #93

The addColumn method of AlterTableBuilder now takes a third callback argument just like CreateTableBuilder.addColumn.

What's new

Kysely now has absolutely no internal dependecies to anything. Not even dynamic ones. The same code runs on node, deno, browser and is compatible with all bundlers out of the box! All dependencies are passed from the outside.

Breaking changes

The dialects now take an instance of the underlying db drivers's pool (or other connection object if a pool is not available). This is how you'd create an instance of Kysely in 0.19.0:

import { Pool } from 'pg'

const db = new Kysely<Database>({
  dialect: new PostgresDialect({
    pool: new Pool({
      host: 'localhost',
      database: 'kysely_test'
    })
  })
})

import { createPool } from 'mysql2'

const db = new Kysely<Database>({
  dialect: new MysqlDialect({
    pool: createPool({
      host: 'localhost',
      database: 'kysely_test'
    })
  })
})

import Database from 'better-sqlite3'

const db = new Kysely<Database>({
  dialect: new SqliteDialect({
    database: new Database('db.sqlite')
  })
})

If you want to initialize the pool lazily when it's used for the first time, you can use a thunk:

import { Pool } from 'pg'

const db = new Kysely<Database>({
  dialect: new PostgresDialect({
    pool: async () => new Pool({
      host: 'localhost',
      database: 'kysely_test'
    })
  })
})

FileMigrationProvider

I also changed the FileMigrationProvider once again, even though I promised never to do that again 😞. This was done to get rid of all dependencies. You now need to use the class like this:

import { promises as fs } from 'fs'
import path from 'path'

new FileMigrationProvider({
  fs,
  path,
  migrationFolder: 'path/to/migrations/folder',
})

Deno and browser builds

There's no more need for the index-nodeless file and it has been removed. You can simply import kysely or the index.ts file from the dist folder. Nothing refers to node or any node library.

• Allow custom migration tables and schema #80
• Allow an existing pool instance to be passed to MysqlDialect and PostgresDialect #81

Breaking changes

UpdateQueryBuilder now takes four type arguments instead of three. The second argument is new and is the table that will be updated. The third one is a union of all the tables that can be referred to.

This only affects you if you've been using explicit types.

What's new

• "update set from" queries are now possible because of the from method in UpdateQueryBuilder
• Raw aliases are now possible when using the as method of a raw sql snippet.