doytowin/doyto-query
Doyto Query is a Java framework that simplifies data access by generating SQL and handling database interactions through annotations and a fluent API. It provides a unified interface for CRUD operations, complex aggregations, and spatial queries across multiple SQL databases, while also supporting MongoDB. The system integrates with Spring Boot to offer automatic configuration, web-layer validation, and caching capabilities.
62.8
Adequate · 3 August 2026
10k
lines of production code
Java
primary language
1
bus factor · 4 authors in all
3
measurements over time
How it got here
2019–2021 · Doyto Query 2.0 modularization
The project underwent a significant architectural shift, reorganizing the codebase into a multi-module Maven structure with distinct layers for API, SQL, JDBC, and web components. This period introduced a comprehensive set of new annotations, core interfaces, and utility classes to support advanced query building, aggregation, and caching features.
30 changes
2022 · Spring Boot auto-configuration and web layer expansion
This period focused on integrating the library with the Spring Boot ecosystem through auto-configuration for JDBC access and web components. It introduced new features for geographic queries and web-layer validation, while significantly expanding test coverage for configuration, error handling, and domain path processing.
20 changes
2023–2024 · SQL dialect and row mapper expansion
This period focused on expanding database compatibility by adding SQL dialects for multiple RDBMS platforms and introducing new JDBC row mapper implementations. The work included refactoring SQL field processing logic and adding comprehensive test coverage for the new features.
9 changes
Survey your own repository
doytowin/doyto-query was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 0166d952dc — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.