Web, Getting Started - MySQL dialect example produces type error about kysely

[koskimas]

I fixed the getting started guide.

[igalklebanov]

Hey 👋

This is a documentation issue - PR's welcome.

1. findPersonById should accept bigint or even number | bigint.
2. Since we're in MySQL context - insertId is not undefined, you can add a non-null assertion as follows: return await findPersonById(insertId!)

[linas-ipxo]

Okay, but then person is defined as

export interface PersonTable {
  // Columns that are generated by the database should be marked
  // using the `Generated` type. This way they are automatically
  // made optional in inserts and updates.
  id: Generated<number>
  ...

and the Person interface doesn't accept bigint in other parts of the examples. I can change everything to bigint, but shouldn't the executeTakeFirstOrThrow() function return insertId typed based on the interface (number)? and not bigint?

[koskimas]

We don't know which property is the auto incrementing primary key. All Kysely sees is the table interface and there's no indication of the primary key. Some tables don't even have it or they have a composite primary key.

Bigint is used because it can hold any integer value, unlike number.

You can easily cast the type using Number(insertId!)