Unexpected token 'E', "Executing "... is not valid JSON

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, sql
Domain
backend, databases

Research direction

Start by reproducing the failed table-insert operation with READONLY=false and ALLOW_WRITE=true, then inspect the response producing the unexpected JSON error. Identify whether the insert request or its response contains the "Executing" text; done means data can be inserted and the operation returns valid JSON.

Written by the indexing model from the issue text.

Description

unable to insert the data into the tables and only able read the data from the tables

were even after make flag setted :
"READONLY": "false",
"ALLOW_WRITE": "true",

Dominant language
HTML
Stars
331
Forks
208
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure-Samples/SQL-AI-samples

All issues in Azure-Samples/SQL-AI-samples

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.