explaingit

abel533/mapper

7,382JavaAudience · developerComplexity · 2/5LicenseSetup · moderate

TLDR

A MyBatis plugin for Java that provides ready-made database operations (fetch, save, update, delete) for single tables, so developers don't have to write the same boilerplate for every table in their app.

Mindmap

mindmap
  root((repo))
    What it does
      Auto CRUD for tables
      No join support
      Cuts boilerplate
    Tech stack
      Java
      MyBatis
      Spring Boot
    Versions
      Spring Boot 4
      Spring Boot 3
      Spring Boot 2
    Related tools
      mybatis-mapper
      PageHelper plugin
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Add automatic CRUD operations to any MyBatis-backed Java project without writing repetitive SQL by hand.

USE CASE 2

Build a Spring Boot web app with database access faster by reusing pre-built single-table queries.

USE CASE 3

Upgrade an older Spring Boot 2 project to Spring Boot 3 or 4 while keeping the same mapper plugin in place.

Tech stack

JavaMyBatisSpring Boot

Getting it running

Difficulty · moderate Time to first run · 30min

Pick the correct branch to match your Spring Boot version (4, 3, or 2) or the plugin will not work correctly.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

This repository is a plugin for MyBatis, a Java library that helps applications read from and write to databases. The plugin is called MyBatis Common Mapper, and its purpose is to cut down on repetitive code. When using plain MyBatis, developers must write specific instructions for every basic database action: fetching a record, saving a new one, updating an existing one, deleting one. This plugin provides ready-made versions of all those common operations so developers do not have to write them from scratch for every database table. The plugin works with single-table operations only. Queries that pull data from multiple tables at once (called joins) are not covered, those still need to be written manually. This is a deliberate scope decision, keeping the plugin focused and simple. There are three maintained versions corresponding to different generations of the Spring Boot framework, a popular tool for building Java web applications. The newest branch supports Spring Boot 4 and requires Java 17 or newer. An older branch supports Spring Boot 3, and a further branch supports Spring Boot 2 with Java 8. The README notes that developers starting new projects should consider a newer sibling project called mybatis-mapper, which achieves the same goals with a cleaner architecture that does not require modifying the underlying MyBatis libraries. The README is written in Chinese and is aimed at Chinese-speaking Java developers. It links to documentation on both GitHub and Gitee (a Chinese code hosting platform), as well as a book about MyBatis written by the same author. The project is open source under the MIT license and has been maintained across multiple major versions of the Spring ecosystem. The author also maintains a pagination plugin for MyBatis called PageHelper, which is mentioned as a companion tool.

Copy-paste prompts

Prompt 1
I'm using MyBatis in a Spring Boot 3 Java app. Show me how to add the abel533/mapper plugin as a Maven dependency and get automatic select, insert, update, and delete for a User table.
Prompt 2
How do I configure MyBatis Common Mapper for Spring Boot 4 and Java 17? Walk me through setup from pom.xml to first working query.
Prompt 3
I have an existing MyBatis project with hand-written SQL for basic operations. How do I replace those with abel533/mapper so I stop duplicating code across every table?
Open on GitHub → Explain another repo

← abel533 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.