praeclarum / praeclarum/sqlite-net
Add extended error code in SQLiteException
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
When a SQLiteException is thrown we cannot handle properly the error because we don't have enough information about it.
For example, when a primary key constraint exception occur, when only know it's a constraint exception but we don't know which one.
You already have a test when you throw a NotNullConstraintViolationException but there is so much exception missing.
I think it could be good to add inside SQLiteException the extended error code.
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 SQLiteException and the existing test for NotNullConstraintViolationException, then inspect how SQLite error information is currently exposed. Add the extended error code to the exception and add coverage showing that distinct constraint errors can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sqlite
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100