Wrap storing steps in a transaction
Open
Nobody has claimed this yet.
1. to develop
26 feedback
feature: sync
skill:backend
technical debt
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Wrap this in a transaction so that reading the current version, increasing and writing steps is an atomic operation.
Should be easy with https://docs.nextcloud.com/server/latest/developer_manual/basics/storage/database.html#transactions
Originally posted by @juliushaertl in https://github.com/nextcloud/text/pull/2971#discussion_r1081033209
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 storing-steps context in pull request #2971 and read the linked Nextcloud transaction documentation. Identify where the current version is read, steps are increased, and the result is written; done means those operations run atomically within one transaction.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100