Forum Discussion

msturzen's avatar
msturzen
Frequent Visitor
21 days ago

GraphQL update... mutation for Fabric SQL DB failing

Hi everybody,  I want to update items in a Fabric SQL DB via GraphQL mutation query. But that fails with "InternalServerError" (and nothing else).  What I tried:  ❌ mutation update.... ✅ mutatio...
API for GraphQL
data engineering
ipkus's avatar
ipkus
Frequent Visitor
21 days ago

Yes, GraphQL can be slightly sensitive when it comes to mutations. We have been able to implement several mutations via strored procdures.  

 

Looks like your mutation has gotten classified as a write-only (Mutation). This means it doesn't produce a Query node. GraphQL schema generation requires at least one Query field by spec — without it, schema validation fails. In the absence of a Query field, schema validation cannot be completed successfully.

Also, make sure Referenced tables are present and accessible in the underlying data source. If the required tables are unavailable, the stored procedure may fail and return a SQL error.

msturzen's avatar
msturzen
Frequent Visitor
20 days ago

Thank you so much for your reply ipkus. and confirming using a stored procedure is a way to enable updates.

Regarding your other statements:

  • What do mean by "slightly sensitive"? Is it pure luck for mutations work? Do I have to roll a D20? (sorry for being grumpy here, not your fault)
  • Is there anything I can do to get rid of that write-only classification?
    • Querying the resource works just fine --> (naive) conclusio: Seems not be write-only
    • What is a Query field? ROWID, other fields of the resource?
  • Thanks for hinting at availability of Referenced tables. In my case there no references. 
  • Unfortunately I do not see any SQL error in the response and Fabric SQL DB is very limited wrt monitoring. Any ideas for this?