I tried different table names like user, User, "user", "User" etc., but as the error is always the same I do not know what the cause is. Simple lookups as SELECT 1; do work so the access to Data Connect is not the problem, which I believe would result in a different error anyway.

I tried different table names like user, User, (削除) "user" (削除ここまで), "User" etc.[Edit: Turns out I tried all except "user", which is the correct name], but as the error is always the same I do not know what the cause is. Simple lookups as SELECT 1; do work so the access to Data Connect is not the problem, which I believe would result in a different error anyway.

I tried different table names like user, User, "user", "User" etc., but as the error is always the same I do not know what the cause is. Simple lookups as SELECT 1; do work so the access to Data Connect is not the problem, which I believe would result in a different error anyway.

Edit: When removing the SELECT id FROM new_recipe - as Pedro correctly mentioned - the same error still gets thrown.

I tried different table names like user, User, "user", "User" etc., but as the error is always the same I do not know what the cause is. Simple lookups as SELECT 1; do work so the access to Data Connect is not the problem, which I believe would result in a different error anyway.

When replacing the _execute SQL statement with a gql mutation the query works as expected:

await dataConnect.executeGraphql(
 `
 mutation InsertRecipe(
 $param1: String!,
 $param2: String,
 $param3: String!,
 $param4: String!,
 $param5: [String!]!,
 $param6: String!,
 $param7: Int!,
 $param8: Boolean!
 ) {
 recipe_insert(data: {
 title: $param1
 authorId: $param2
 subtitle: $param3
 description: $param4
 foodTypes: $param5
 imageUrl: $param6
 estimatedMinutes: $param7
 isTest: $param8
 })
 }
 `,
 {
 variables: {
 param1: draft.param1,
 param2: draft.param2,
 param3: draft.param3,
 param4: draft.param4,
 param5: draft.param5,
 param6: param6,
 param7: draft.param7,
 param8: draft.param8,
 },
 }
);