Rainbow.Database - some extension points are needed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
- Expose (read-only) Connection property;
- Expose (read-only) Transaction property;
- Mark Dispose() method with 'override'.
1 & 2 are needed when using Rainbow.Database alongside another DB access technology (think EF) within the same transaction.
3 is obvious. Sometimes, i want to clean up some more stuff in my Database-derived class.
I can create a PR if it ppl think this is going to be useful. I'd like to hear some opinions, especially from contributors.
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
Locate the Rainbow.Database class and inspect its current Connection, Transaction, and Dispose members. Confirm the requested read-only exposure and Dispose override fit the existing API, then verify that derived classes can extend cleanup and share the transaction with another database access technology.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- database
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100