DriverManager
DriverManager sits in JDBC — Java talking to a database with SQL. Five steps: driver → Connection → Statement/PreparedStatement → ResultSet → close (try-with-resources).
For DriverManager — prefer PreparedStatement. Never paste user input into SQL with +. That is SQL injection.
DriverManager session: connection URL, user, and password. ResultSet is read row by row with next(). Close everything when done.
Let's take this on the board with one tiny Main class — no extra files. DriverManager — this Main really runs. If MySQL school DB is up, it prints Connected to school DB. If not, catch prints No DB yet + exception class. Steps stay: connect → prepare → execute → read → close. Start from main, go line by line, and stop at each print. That output is the proof for DriverManager.
List the 5 classic JDBC steps in order.