tonid
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
Everything works now. Thanks a lot !
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
at least ts , will see for default now
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
Updated it and it works now 🙂
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
Thanks! Yes its likely something that directus does on its level.
When i try to do it as you showed i get ts error:
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
16 replies
DTDrizzle Team
•Created by tonid on 9/13/2023 in #help
PostgresError: null value in column "id" of relation "pairs" violates not-null constraint
That makes sense. However, I think that changing the database like that would:
- Delete tables that I removed from the schema, which Directus uses internally.
- Potentially create a change in some table that Directus doesn't know how to deal with.
My idea was to use Directus to create tables, generate schema using introspect with drizzle-kit, cleanup the schema and then manually keep it in sync with database
16 replies