sql.raw() does not get columns from Table object
``typescript
sql.raw(date_format(${MyTable.mycolumn}, "%d-%m-%Y") like "%${search}%") // This errors
sql.raw(date_format(${MyTable.mycolumn.name}, "%d-%m-%Y") like "%${search}%"`) // This Works!
...UPSERT operation not working for SQLite/Turso
.returning()  and its not working. I expect:
- UPDATE: rows which include the PKs "id" 
- INSERT: rows which DO NOT include the PKs "id"
the code is as follows (I've followed the docs and tried some variants):
```ts...Difference between dialect and driver
equivalent of a sql query in posgresql
Unable to setup supabase with drizzle
drizzle-kit: v0.21.2 
drizzle-orm: v0.30.10
drizzle-kit: v0.21.2 
drizzle-orm: v0.30.10
I made a change, yet generate says "No schema changes, nothing to migrate"
balance: integer("balance")
and drizzle-kit generate:pg generated the correct migration:...How to use libsql features in migrations
libsql> ALTER TABLE emails ALTER COLUMN user_id TO user_id INT
then I get an error because libsql> is not recognized, but then what is the point of writing driver: "turso" in my config file? isn't the turso driver what tells drizzle it can use libSQL features?...Get raw SQL string with parameters
query.toSQL() and then do a string-replace on ? with toSQL().sql | toSQL().params.
My questions are:
-  is this the right way to do it?...Rename conflicted column (postgres)
(drizzle-kit) npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memo
equivalent code drizzle
drizzle schema type error

drizzle-kit push not updating table schem
[Eslint]Drizzle `.delete()`
.delete()....
t3stack, multi-file schema, can't use with.

Two tables that references each other

unsigned bigint casted to string
Migrations not changing on adding notNull
.notNull on some column ?
Currently, my use case is that have a first migration that has created the table, but now the second migraiton (adding the notNull) doesn't actually create a migration....Is there a way to simulate mode: 'string' for bigint?
drizzle-kit push inconsistent with database with migrations already applied
drizzle-kit push command should look at changes that I have made and push these up to the database before I make a migration to commit that change for good? Anyway, here's my issue...
So, I've got a pg_enum defined:...