How to handle versioning of database objects.
Sqlite JSON
stringify
and parse
JSON myself when using Kysely, but it looks like I can addColumn("myColumn", "json")
. However, when I try to insert values as JSON, I get TypeError: SQLite3 can only bind numbers, strings, bigints, buffers, and null
.
If I strigify
my JSON first, it adds to the database properly, but the Kysely gives me type errors. Should I have my Database
table column of type string
when I am passing type "json" to Kysely?...case() return boolean (castTo doesn't work?)
TINYINT convert to bool
CASE with subquery clause
{ name: string }
:
```ts
eb.case()
.when('re.type', '=', 'company')...Ad hoc custom column type
Creating a table within a schema using a column from a table in another schema
Guidance to create a generic wrapper over Kysely
Kysely
instance, a database table name and an array of column names.
- The function will return an authenticator instance you can use to perform user lookups during Login. The internals of this function are not important for this discussion.
...Any way to docutype a Column as `@deprecated`?
@deprecated
type identifier in the Table type definition comments to be used in queries, is there a way to make it work with Kysely?Help with CTE query
Error this query cannot be compiled to SQL
``
await trx.executeQuery(
sql<any>
ALTER SCHEMA ${current.subdomain} RENAME TO ${subdomain};`...``ts
await sql
.raw(
ALTER SCHEMA "${current.subdomain}" RENAME TO "${subdomain}"`)
.execute(trx)...Object literal may only specify known properties, and 'clientId' does not exist in type 'InsertObjec

Reuse subquery selects
myUnion().as('u')
Use JSON key as text
->
to ->>
, doh!Typing issue when working with onConflict
Json
to string
. This is something Kysely should handle, but it's really difficult in that case. What I'd do is this
```ts
export type Json = ColumnType<
JsonValue,...getting Error: relation "myschema.kysely_migration_lock" does not exist
Error: relation "myschema.kysely_migration_lock" does not exist
.
Do I have to create the kysely tables manually to be able to run the migrator?
I would have expected that the migrator creates these tables when they do not exist....What is easiest way to get count alongside data for pagination?
SELECT COUNT(id) from table_name
. is this legit?Reusable CTEs that depend on previous CTEs
eligibleChats
instead of chatMessages
, then you can do it like this
QueryCreator<DB & { eligibleChats: { chatId: string } }>
QueryCreator<DB & { eligibleChats: { chatId: string } }>
`update set from`
update set from
sql syntax. So far, I've been unable to figure out how (in lieu of dropping down to raw sql).
We are planning to craft many of our update statements as batch operations in our repository layer, so this pattern will be used heavily.
Here's some example sql to make it clear (hopefully) what I'm trying to do...