Renaming pgEnum results in truncation?
status
on two different tables, and Drizzle just chose one of the enums for the migration and didn't include the other. I was able to solve this by just changing the column names to project_status
and comment_status
(which might be better anyways, so its fine). But when pushing that migration I got a new warning saying that changing the column datatype from status
to project_status
would truncate the table, even though neither the enum datatype itself nor the default value had changed at all. Just the name.
So I guess I'm just wondering if anyone has encountered anything similar, and if you were able to find a solution, or if this might be worth opening issue over. Or rather if I just clearly have a misunderstanding of how PG works, please let me know lol. Thanks in advance!...Drizzle Kit + Planetscale example?
Issue with Jest tests in Next.js
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
explain relationName please
"relationName is already supported, just not documented. So you can use it exactly as you've described. You'll just need to add where clauses to the corresponding with entries."
"relationName is already supported, just not documented. So you can use it exactly as you've described. You'll just need to add where clauses to the corresponding with entries."
Error While db-push
description
to it and tried to push, it gave me this error. I wonder why.Type error: Type parameter has a circular constraint
next build
. Thought I'd drop it here in case anyone else has run into it or has any tips for debugging:
```
- info Checking validity of types...
Failed to compile....There is not enough information to infer relation
Getting Invalid default on timestamp when pushing schema to Planetscale
How to flatten select results from query with left joins (one-to-many)?
"mode" not defined in drizzle config 0.28.1
how to convert serial to uuid type
todos
table with id as serial
type, migrated and pushed it to my db, now I wanted to change the type to uuid
but the following error appears on my console
PostgresError: column "id" cannot be cast automatically to type uuid
...how to make a session using drizzle
Aws Rds with drizzle
BadRequestException: ERROR: relation "fuc" does not exist
Position: 13; SQLState: 42P01
I get this...Error: Can't find meta/_journal.json file when trying to apply migrations in a lambda
sls invoke local -f db_run_migrations
command
This is my folder structure and lambda handler...Nested joins / where on relation
order
relation - order.date
is the field I want to filter by. However, I've noticed that filtering by relations is not yet supported. How do I write the query with joins? I can't figure out how to created nested joins (subOrders -> order
and subOrders -> product -> kitchens -> kitchen
etc.)
This is my query:
```ts
const suborders = await db.query.subOrders.findMany({...Relational queries with planetscale - findMany etc undefined
how to use serial within compound primary key
Multiple relations
When using with in relational queries the `orderBy` function is not typed.
where
to filter the table....