tursodatabase / tursodatabase/libsql
Does not immediate saved into db?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
I have a prepare statement that insert into table.
When I submitted 1st form submission, I could not find any row appear in my table, and test 2nd form submission, then I realised the 1st row will then appear but not the 2nd row that will only appear after the next form submission.
Why is this a weird behaviour or a bug?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported prepare statement behavior and reproduce the two consecutive form submissions against the table. Inspect the relevant SQLite/libSQL transaction and statement-lifecycle behavior; done means determining whether this is a libSQL bug or a missing caller action, with a minimal reproducible case if a code defect is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100