MySQL: development and safe operations
Six lessons, 30 questions, and six MySQL cases on data, queries, InnoDB, integration, releases, and recovery.
Objectives and progression
Independent course with six modules, explained practice, and fictional application and APS cases. Internal assessment of 24 decisions in 60 minutes. MySQL 9.7 LTS with InnoDB reference, distinguished from the 26.7 Innovation line. The 9.7.3 note applies only to the Docker image, without automatic equivalence across packages. It is not associated with an external exam. Examples reviewed against documentation without execution on a MySQL engine.
Audience: Developers, APS/L3 teams, and technical managers responsible for MySQL applications.
Prerequisites: Basic SQL and concepts of transactions, networking, and application development.
300 estimated study minutes
- Choose representation, comparison, and validation around data meaning.
- Explain the intended result before optimizing access.
- Preserve the business unit through concurrency, deadlocks, and timeouts.
- Separate values, SQL structure, and execution identity.
- Plan compatibility, locking, and recovery before changing structure.
- Distinguish snapshots, replication, and historical recovery in the application contract.
Modules
- Types and data contracts
- Deterministic queries and plans
- InnoDB transactions and error paths
- Safe integration and effective identity
- Schema, DDL, and release acceptance
- Recovery and cross-server consistency
Continue learning
References and version
MySQL 9.7 LTS with InnoDB reference semantics
- Innovation and LTS release tracks · 2026-09-30
- 9.7.3 Docker-image-only patch scope · 2026-09-30
- Exact decimal data types · 2026-09-30
- Temporal types and session time zones · 2026-09-30
- Case and accent sensitivity in collations · 2026-09-30
- NULL comparison semantics · 2026-09-30
- Aggregate NULL handling · 2026-09-30
- Strict SQL modes · 2026-09-30
- Deterministic grouping and functional dependence · 2026-09-30
- Composite index prefixes · 2026-09-30
- EXPLAIN and executed ANALYZE · 2026-09-30
- Deterministic ordering with LIMIT · 2026-09-30
- Filesort and memory or disk · 2026-09-30
- InnoDB snapshots and locking reads · 2026-09-30
- FOR UPDATE and SKIP LOCKED · 2026-09-30
- Statement versus transaction rollback · 2026-09-30
- Deadlock prevention and retries · 2026-09-30
- Parameter marker scope · 2026-09-30
- Prepared statements and injection prevention · 2026-09-30
- User and host account identity · 2026-09-30
- Granted and active roles · 2026-09-30
- Invoker and definer security context · 2026-09-30
- TLS server identity verification · 2026-09-30
- DDL and implicit commits · 2026-09-30
- Atomic DDL versus transaction rollback · 2026-09-30
- Metadata lock lifetime · 2026-09-30
- Operation-specific online DDL capabilities · 2026-09-30
- Logical snapshot backup limitations · 2026-09-30
- Backup and binary-log recovery · 2026-09-30
- Replication and asynchronous operation · 2026-09-30
- Executed GTID waits and timeout results · 2026-09-30
What you will explore
0 / 6Types and data contracts
Choose representation, comparison, and validation around data meaning.
Deterministic queries and plans
Explain the intended result before optimizing access.
InnoDB transactions and error paths
Preserve the business unit through concurrency, deadlocks, and timeouts.
Safe integration and effective identity
Separate values, SQL structure, and execution identity.
Schema, DDL, and release acceptance
Plan compatibility, locking, and recovery before changing structure.
Recovery and cross-server consistency
Distinguish snapshots, replication, and historical recovery in the application contract.