Knex.js migrations, drawn as a database diagram

/**
 * Owners, pet types and pets.
 *
 * Written with Knex's own schema builder, which is what a Knex migration
 * normally is: the same file emits PostgreSQL and MySQL DDL, so one upload
 * draws on both engines.
 *
 * Named constraints are passed as a plain string - table.primary(cols, name).
 * The documented object form, table.primary(cols, { constraintName: name }),
 * is rendered wrongly by MySQL's table compiler inside createTable (knex
 * 3.3.0): it wraps the whole object and emits
 * `constraint \`pk_owners\` as \`constraintName\` primary key (...)`.
 */
exports.up = async function up(knex) {
  await knex.schema.createTable('owners', (table) => {
    table.integer('id').notNullable();
    table.string('first_name', 50).notNullable();
    table.string('last_name', 50).notNullable();
    table.string('address', 255);
    table.string('city', 80);
    table.string('telephone', 20);
    table.primary(['id'], 'pk_owners');
  });

  await knex.schema.createTable('types', (table) => {
    table.integer('id').notNullable();
    table.string('name', 80).notNullable();
    table.primary(['id'], 'pk_types');
  });

  await knex.schema.createTable('pets', (table) => {
    table.integer('id').notNullable();
    table.string('name', 50).notNullable();
    table.date('birth_date');
    table.integer('type_id').notNullable();
    table.integer('owner_id').notNullable();
    table.primary(['id'], 'pk_pets');
    table.foreign('type_id', 'fk_pets_types').references('id').inTable('types');
    table.foreign('owner_id', 'fk_pets_owners').references('id').inTable('owners');
  });
};

exports.down = async function down(knex) {
  await knex.schema.dropTableIfExists('pets');
  await knex.schema.dropTableIfExists('types');
  await knex.schema.dropTableIfExists('owners');
};