Add method to drop scheme from database
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by locating the Database entry point and the existing scheme and table-removal operations. Trace how table references to schemes are represented, then add coverage for dropping an unused scheme and for rejecting a scheme still used by a table. The work is done when both cases have clear, tested behavior.
Written by the indexing model from the issue text.
Description
To avoid that a user removes a scheme that is used in a table, it could make sense to introduce Database.drop_scheme() to raise an error in that case.
- Dominant language
- Python
- Stars
- 13
- Forks
- 2
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from audeering/audformat
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
documentation enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in audeering/audformat
Similar issues
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backendPossibly taken @debesh-biswas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
`rx.Model` event arguments emit `PydanticDeprecatedSince20` once per payload keyPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
reflex-dev/reflex#7634 · 1 comment ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
topoteretes/cognee#6239 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ranaroussi/yfinance#3009 ·
Maintainers usually reply within 1 day
-
Test discovery aborts on GPU builds without cuStateVec: check_cuStateVec expects a failed result but set_config() now raises RuntimeErrorPossibly taken @dmeliksetian claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Qiskit/qiskit-aer#2495 ·
Maintainers usually reply within 1 day