JDBC Disadvantage analysis

* The JDBC code is cumbersome, and each time JDBC needs to write "the same" six steps.

* SQL cannot be configured, in JDBC programming SQL statements are written in the Java source program, SQL statements often change (business changes), after SQL changes, need to re-modify the Java source code, recompile, redeploy, restart the server.
Obviously, this design violates a development principle: open/Close principle (OCP)
OCP: Open to extensions, close for modifications. (OCP is not part of a programming language, it is a part of software engineering)
After modification to ensure security, a re-test is required.

* The processing of result sets in the JDBC program is too cumbersome.
We need one out of the result set, then we create an object ourselves, and we have one set, and finally we have to put the object in the collection.
MyBatis can be done automatically. (Auto-map, MyBatis can automatically map records in database tables into Java objects.) ）

JDBC Disadvantage analysis