mybatis-patterns

Topics in the source

• MyBatis Patterns
• When to Activate
• How It Works
• Examples
• Parameter Binding and SQL Safety
• XML, Result Types, and Result Maps
• Dynamic SQL
• Transactions and Sessions

Use MyBatis when SQL control and explicit mappings matter. Keep SQL readable, make mapper contracts small, and put business transactions in the service layer. Pair this skill with springboot-patterns for application structure, database-migrations for schema changes, postgres-patterns or mysql-patterns for engine-specific SQL, and security-review for untrusted input and access-control concerns. Adding or reviewing MyBatis mapper interfaces or XML files Choosing between XML mappers, annotation mappers, and generated SQL Designing resultMap mappings, joins, nested collections, or projections Reviewing dynamic SQL, parameter binding, pagination, or batch writes Debugging N+1 queries, slow statements, connection use, or transaction bugs Integrating MyBatis-Spring into Spring Boot or an XML-first legacy application Use a thin mapper for persistence operations and keep business rules in a service. A typical flow is: Register mappers once, either with @Mapper on each interface or with @MapperScan for a package. Do not mix registration approaches casually. Keep the XML namespace equal to the mapper interface's fully qualified name. Give each statement a stable, descriptive id; treat mapper

This is an excerpt. Refer to the complete source and its current requirements.