Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Handling errors

Open
#20 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
sqlite
Domain
databases

Research direction

Review the current start table and test.sql to understand how valid data is loaded and how the exercise currently presents database behavior. Decide which error-handling approach is appropriate for students and define test cases that make completion observable; the issue does not yet specify a file change or a settled expected outcome.

Written by the indexing model from the issue text.

Description

I have an idea for handling errors.

Normally you would deny faulty data to be inserted into the database before it happens.
Currently, we have a start table, that has valid data. We could change this method to insert one row after another and let the students create checks and catch the error message somehow.
I am unsure how obvious these error test cases would be for those who read our test.sql file.

As an alternative, we could ask them to clean erroneous data from the table and check if it is still there.

Do you have other ideas?

Dominant language
Jinja
Stars
9
Forks
15
Avg merge
10h 5m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from exercism/sqlite

All issues in exercism/sqlite

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.