1
Composite keys support (FORBIDDEN, Primary key is missing)
Source: directus/directus#25560 · opened by @kravetsone
Summary Currently, if you want to setup directus for existing database some tables with composite primary keys are not working in Directus right now (It throw Forbidden error on client side and doesn't have a primary key column in server side logs) [It is known limitation]( <img width="1194" height="215" alt="image" src=" /> Also this is logged: [12:12:47.483] WARN: Collection "channel_to_monitoring_task" doesn't have a primary key column and will be ignored It would be fine to fix this someday!! As workaround you should go away from composite primary keys Basic Example _No response_ Motivation Because it makes using directus with an existing database so difficult. Detailed Design Just support it Requirements List Must Have: • A • B Should Have: • C Could Have: • D Won't Have: • E Drawbacks No reasons to not do this …
No pledges yet. Be the first to back this.
Comments
Similar requests
In flows, why {{$trigger.keys}} for the key on action create, and {{$trigger.keys[0]}} on action update
1 vote · 0 comments
Improve error message for composite primary key failure
1 vote · 0 comments
Composite key support
111 votes · 0 comments
Enable PATCH Endpoint to Accept Arrays for Bulk Updates (Update Many Items with Unique Values Using Unique Key, Composite Key, or Query)
7 votes · 0 comments
Ability to filter items creation: skip creation or replace by an existing item
12 votes · 0 comments
No comments yet.