Yesterday I added some new fields with relations to Directus instance (hosted on DigitalOcean), using sqlite 3) and updated my graphQL file accordingly, also the types for TypeScript. Everything works fine in Postman, but in Nuxt 4 I get the error:
data = {errors: Array(1)}
"GRAPHQL_VALIDATION"
{line: 22, column: 22}
"Field \"additional_artists\" must not have a selection since type \"String\" has no subfields."
{message: 'Field "events" must not have a selection since type "String" has no subfields.', locations: Array(1)}
{message: 'Field "events" must not have a selection since type "String" has no subfields.', locations: Array(1)}
{message: 'Field "performances" must not have a selection since type "String" has no subfields.', locations: Array(1)}
"GraphQL validation error."
indicating that all those relational fields I created are returned as String types instead of relations. In order to make sure I didn’t mess up with Typescript, I also tried it using plain JS - but the errors persist. Eventually I also tried using the RestAPI, which, works totally fine.
Just to be clear: these are new relations that I created yesterday or the day before. Old relational data works fine. (And there are a lot of relations!)
Since I used the latest Directus verson 11.10.2, I downgraded to 11.10.1 (which didn’t start up) and eventually 11.10.0. The errors remain.
Eventually I used Claude and Gemini with Directus’ mcp servers and did my best to define a specific sub agent and what not. But they got lost in a vicious circle.
I could move to PostGres, but actually I really want to keep using SQLite… and my guts tell me that the DB itself is not the problem.
I should also mention that I tried to set MAX_RELATIONAL_DEPTH to 15, but removed that again.
So before I go ahead and file a bug on github, I wanted to ask you , if anybody else ever has encountered a similar situation? Maybe even kows what’s going on?