Migration Halts

drizzle-kit libsql extensions
[Turso] Undefined primaryKey on push
drizzle-kit push, I get this error: Cannot read properties of undefined (reading 'primaryKey')
I have also tried to introspect and generate the new SQL script, but I get this error: LibsqlError: SQL_NO_STATEMENT: SQL string does not contain any statement. Is there a way to fix this? Not sure what I should do as a first-time drizzle user...Joins with results in arrays
query with
Issue with drizzle-graphql Entities Not Working Well with GraphQL
drizzleEntities with my GraphQL schema, particularly when extending or manipulating types. Using getFields() to spread fields from drizzleEntities.types.UsersItem results in errors like:
```...
Help Needed: Error with Arguments in GraphQL Resolver Using Drizzle ORM, Serverless, and TypeScript
conditional unique constraint
Help Needed: `UnhandledSchemeError: cloudflare:sockets` with Drizzle ORM and `runtime = "edge"`
export const runtime = "edge";, I encounter the following error during compilation:
```...cannot generate a migration file.
npx drizzle-kit generate it gives me No config path provided, using default 'drizzle.config.ts' but it doesn't create any migration file nor gives me any error. i have attached image of my drizzle.config.ts and schema.
Create a schema but hide from push, migrate and generate
Delete an item from an object
Is there more elegant way to infer enums?
type TransactionReason = (typeof transactionReasonEnum)['enumValues'][number]
But I wonder if Drizzle happen to have built-in way to infer TypeScript union from PostgreSQL enum....seed

problems with config file dialect for PostgreSQL
Properly setting timestamp column
timestamp to match some data that I am getting. This is what my schema looks like:
```ts
export const weeksTable = pgTable(
'weeks',...
table with multiple possible one-to-many relation, but not many-to-many
Upgrading from drizzle-kit 0.21 ~> 0.24 didn't work, had to revert
drizzle-kit up seems to need an actual database connection, which was suprising. I run postgres locally in development but then there's a server as well, so this step made me nervous. More specifically, it feels like the generated migrations should stand alone without any particular server version.
Am I missing something? Again, love the software, so happy to step through any of this if it's helpful. In the meantime I'll just pin my version and try again in a few releases....create custom types in postgresql and still have type support using drizzle orm
⚠ Error - Top-level await is currently not supported with the "cjs" output format
drizzle_test@0.1.0 db:migrate...