Updating a Supplier Catalog is a hands-on SQLite project for learners with basic terminal familiarity. Receive parts catalogs for a repair shop, separate usable data from invalid or contradictory records, and update the right stock items without losing the shop’s own shelf notes.
Two Guided Labs first build a reusable delivery inspection, then apply newer editions and handle repeated or older deliveries. An independent Challenge changes the suppliers, part identities and edition conflicts. Every unit starts with its own prepared database and files.
What You Will Learn
- Read SQLite tables and connect a stock item to its supplier and local information.
- Stage a CSV as text so invalid values remain visible before conversion.
- Validate identifiers, titles, integer prices and revision numbers with reusable SQL views.
- Distinguish identical repeated records from contradictions about the same edition.
- Use a composite identity and conditional UPSERT to accept new items and advance only newer values.
- Preserve local shelf notes, reject unsafe records, and repeat compatible imports without duplicating items or rolling stock backward.
Who This Course Is For
This course is for beginners ready to use a database for a complete receiving task rather than isolated SQL commands.
Prerequisites: Basic terminal input and path navigation. SQL, CSV staging, SQLite shell commands, views, conflict checks and transactions are explained before use. No Python programming, website development or database-administration experience is required.
Learning environment: SQLite, a repair shop database and synthetic supplier CSVs are prepared in a browser-based Terminal. You work with real database rows and save reusable SQL files. The supplied data, filenames and command output remain in English.
Frequently Asked Questions
Do I need to install SQLite or provide supplier data?
No. The database tools and fictional deliveries are prepared. You focus on inspection and safe updates.
Why not import the CSV directly into stock?
A delivery may contain invalid numbers, unknown identities or contradictory editions. Staging preserves the original text so you can decide what is safe before changing persistent stock.
How does the Challenge differ from the Guided Labs?
It changes supplier codes, part relationships and which editions conflict. Apply the taught inspection and update methods independently; the Guided Lab’s final values do not solve it.
Does this cover every possible CSV or a production synchronization system?
No. You work within a clearly defined five-field delivery format and bounded positive integer values. The project does not implement concurrent synchronization, external data collection or a backup system.
