linksplatform / linksplatform/Data.Doublets
Handle read and write operations mixing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
It should be impossible to use write operation (Create, Update, Delete) inside read operation (Each).
At the moment it is possible, but this is unsafe, it can lead to traversing indexes tries and changing them at the same time. At the moment, we don't have traversing algorithms that can handle these situations. I also don't think it should be solved by changing these algorithms.
The workaround at the moment is to use ReaderWriterLock via ISynchronizedLinks.
Contributor guide
No contributing guide indexed for this repository
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
The issue identifies Each and Create/Update/Delete operations, with ISynchronizedLinks as the current workaround. Start by tracing how these operations interact with traversal and index code; done means writes attempted during Each are prevented and the unsafe modification case is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100