Open pingu2k4 opened 8 months ago
PR #1883 might fix this issue. We will investigate why that wasnt merged and fix this issue.
@pingu2k4, I tried with the latest release.
passing the value in query itself. (Working fine).
passing in the variables (issue)
We will see what's causing the second approach to fail. For now you can use the first approach with the latest release and it should work fine.
Hi @abhishekkumams - Thanks for taking a look.
We are using strawberry shake to generate our classes for querying GQL, and whilst I imagine we could set things up like that, the reality of our actual use cases is that most models we are creating etc like this have dozens of properties, so needing to specify each of them individually would become quite a pain rather than using a single object containing all the properties.
The same issue exists when using a DateTime in the same way also.
What happened?
Hey. I have a table in a minimal repro, which you can create with the following:
Go ahead and
dab add
this entity into your config.The schema that DAB will be using has a
CreateNewTableInput
where the id field is nullable, which is accurate as the DB can handle generating the id for us.However, if we run the mutation by passing the item in as a variable, then it fails with an internal server error.
Example mutation:
variables:
The response I get back from DAB is the following:
Version
0.9.7+e560142426d1c080b9fd7b7fabff51a276f6bf61
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI), Static Web Apps (SWA)
Which API approach are you accessing DAB through?
GraphQL
Relevant log output