Geeting error while migration even though evrything is correct

using array of ids as a where clause, using magic sql operator
``
const query = sql
        SELECT 
          ${Statistics.variantId}, ...WHERE x IN (${sql.raw(variantIds.join(','))}) will for now at least not make your site explodeType error when using subquery in where
Argument of type 'Aliased<string>' is not assignable to parameter of type 'Column<ColumnBaseConfig<ColumnDataType, string>, object, object>'.
  Type 'Aliased<string>' is missing the following properties from type 'Column<ColumnBaseConfig<ColumnDataType, string>, object, object>': table, name, primary, notNull, and 14 more.
Argument of type 'Aliased<string>' is not assignable to parameter of type 'Column<ColumnBaseConfig<ColumnDataType, string>, object, object>'.
  Type 'Aliased<string>' is missing the following properties from type 'Column<ColumnBaseConfig<ColumnDataType, string>, object, object>': table, name, primary, notNull, and 14 more.

Integration tests in new pgSchema
schema validation enforcement
Unable to run drizzle query for supabase
drizzle.ts:
```ts
import { drizzle } from 'drizzle-orm/postgres-js'
import postgres from 'postgres'...drizzle with expo-sqlite
Drizzle SQLite not implicitly handling autoincrement primary key id
Migration and existing policy issues
How to check migration history?
Drizzle-kit detecting random enums?
Drizzle not migrating (SupaBase) when I run npx drizzle-kit migrate
Drizzle-kit push remove interactivity?
drizzle-kit push fails every second time
push.
How can I resolve this? I'm attaching a log below, this is without changing anything in between:...Permission denied during 'migrate' command under locked-down database
public only. When trying to run drizzle-kit migrate, I get a [...] permission denied for database [...] error. Unfortunately, this is all I can provide unless there's a way to get logs that might help.
I have my config defined as
```
// ......"where" clause not found in "with" object

Strange timestamp side-effect introduced to TypeORM when initialized drizzle db client
drizzle-kit and it's amazing. However, while working on the ORM migration from TypeORM to drizzle, I discovered a very strange side-effect that TypeORM timestampz column stops transforming date string to Date object after initialized drizzle db client in the codebase.
For example, in TypeORM, createdAt used to return a Date object (2024-05-01T15:00:00.000Z when doing console log), but after initialized drizzle db client, it becomes the raw string stored in the DB '2024-05-01 15:00:00+00'....IN Statement
Studio infinite loading

DB-Caching?