All courses/Digital

Course 273 · Digital course 36

Change SQL Data with Safe Transactions

Build a local SQLite seat-transfer exercise with before/after totals, an all-or-nothing update, a deliberately rejected change and rollback evidence. Work from supplied original examples and check changed cases.

Before you start

Complete or review Answer Questions with SQL before starting.

Answer Questions with SQL See everything you’ll need

Free download · Original practice data · No external account required. Download the starter pack

What you’ll leave with

A local SQLite seat-transfer exercise with before/after totals, an all-or-nothing update, a deliberately rejected change and rollback evidence.

Start course Start without an account. Sign in to save lesson progress across devices.

Your project

Start with the practice files. Build your project one lesson at a time.

Practice files are free without an account. Sign in to save your project record in My Proof: a description, checklist, and optional work link. Keep the original files in your own app or notebook; saving a project record does not upload them.

  1. Get your materialsDownload practice filesSupplied practice cases, a blank working record, complete lesson instructions, and annotated worked examples.
  2. Make your projectView the project checklist Work in your own notebook, document, or software. Use the supplied practice examples when you prefer.
  3. Keep a private recordSave a project record Sign in to save a description and checklist, then return to update them.
Course handbook

Know the route before you begin.

Here’s what you’ll need and what you’ll make. You can return to this guide during any lesson.

Who this is for

Learners ages 14+ and adults ready for the named prerequisite; no employment or private records required.

Prepare before lesson one
  • Complete or review Answer Questions with SQL before starting.
  • Use a local text editor and a free Python 3.10+ interpreter for Python files, or a current browser for HTML files. Supplied code uses no paid services or external packages.
  • Create a fresh practice folder and use only the supplied fictional inputs. A paper trace is labeled a trace, not an executed test.
Your final project

Finish with proof you can use.

A local SQLite seat-transfer exercise with before/after totals, an all-or-nothing update, a deliberately rejected change and rollback evidence.

Save a project record in My Proof
See project checklist and review criteria

Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.

What to include

  • A seat-transfer contract with total 10 preserved.
  • Two targeted updates with a declared completion boundary.
  • A committed all-or-nothing transfer record.
  • A 5, B 5 and no active transaction after rejection.
  • A parameterized update/lookup record with known-ID validation.
  • A checked seat-transfer transaction packet.

Review and revise

Use these criteria to check your work and choose what to improve.

  • The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
  • Normal, boundary and rejected cases are recorded with expected versus observed results.
  • The changed case has a correct explanation and does not rely on hidden state.
  • The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Three ideas to help you along the way
Three useful ideas

The rules behind the steps.

01

State the contract

Name inputs, permitted states and observable outputs before editing the implementation.

02

Preserve the evidence

Keep the actual source, changed input and expected/observed record so someone can repeat the work.

03

Test the boundary

Check a rejection or changed case and distinguish local practice from real service or native-tool behavior.

What do these words mean?
Key words

Key terms worth knowing.

Transaction
A group of changes accepted or discarded as a unit.
Commit
Finalizing a transaction’s changes.
Rollback
Discarding uncommitted transaction changes.
Parameter binding
Passing data separately from SQL syntax.
Your route

6 lessons.
One useful project.

Work in order the first time. Each lesson makes something the next lesson can use.

  1. 1
    Up next

    State invariants before an update

    Apply state invariants before an update to the supplied case and produce A seat-transfer contract with total 10 preserved.

  2. 2
    16 min

    Write a targeted UPDATE

    Apply write a targeted update to the supplied case and produce Two targeted updates with a declared completion boundary.

  3. 3
    19 min

    Group a transfer in a transaction

    Apply group a transfer in a transaction to the supplied case and produce A committed all-or-nothing transfer record.

  4. 4
    22 min

    ROLLBACK a failed rule check

    Apply rollback a failed rule check to the supplied case and produce A 5, B 5 and no active transaction after rejection.

  5. 5
    19 min

    Use parameters instead of concatenation

    Apply use parameters instead of concatenation to the supplied case and produce A parameterized update/lookup record with known-ID validation.

  6. 6
    24 min

    Verify balances and recovery evidence

    Apply verify balances and recovery evidence to the supplied case and produce A checked seat-transfer transaction packet.

Use the tools

Tools to help you practice.

See all tools
Source transparency

Sources and further study.

Explore the references behind the lessons and take your learning further. Source notes explain access and reuse.

www.sqlite.org — lang_transaction.html
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

www.sqlite.org — lang_update.html
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

docs.python.org — sqlite 3.html
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

Ready when you are

Start with the first useful move.

You’ll always know what to do, what to make, and where to go next.

Start lesson one