Adding Pickup Options to a Shop is a hands-on MySQL project for learners who know basic SQL and terminal navigation. You will extend an existing order system so a new checkout can select a pickup point while the old checkout continues to omit that column. Original order identities, amounts, notes and item relationships must survive.
Two Guided Labs teach compatible expansion, exact historical backfill and separate rule tightening. An independent Challenge transfers those decisions to a repair shop with different desks, defaults and order identities. Each unit provides its own fresh data and ready-to-use Terminal.
What You Will Learn
- Expand a table with an explicit default that preserves legacy omitted-column writes.
- Use approved order-ID mappings instead of guessing historical choices from a name or default.
- Refuse incomplete, duplicate or invalid mappings before a partial business change.
- Enforce non-null valid pickup references while keeping legitimate old and new checkouts usable.
- Separate transactional data changes from MySQL DDL and observe what ROLLBACK cannot undo.
Who This Course Is For
For beginning database developers and MySQL learners who want to evolve an existing schema without discarding its business data. Prerequisites are basic terminal navigation, MySQL connection, SELECT/WHERE, INSERT/UPDATE, columns, primary keys and defaults. The course explains its JOIN, aggregate, temporary-table and transaction patterns before the Challenge.
LabEx supplies Oracle MySQL, original orders and items, an approved historical map, checkout tools and a browser Terminal. You author SQL files; no Python or application programming is required.
Frequently Asked Questions
What will I deliver? Saved expansion, backfill and tightening SQL plus an actual migrated order system. Both prepared checkout versions must work, invalid pickup writes must fail, and protected history and later choices must remain correct.
Does this promise zero-downtime migration? No. Work takes place in a controlled maintenance window with sequential requests. You observe native implicit-commit behavior and learn why wrapping ALTER in a transaction does not provide automatic DDL rollback. This does not establish lock-free deployment or arbitrary concurrent migration safety.
