Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience real numbers from our own analytics — open to see them
–Visitors
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · counted by iTechGuides's own first-party analytics, bots removed, every figure rounded down · how we count

requery review

Free#34 of 51 in Database Query Builders

A focused open-source library for typed queries and compile-time entity generation.

5.6/10Editor score
requery5.6 Visit requery

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For Java and Kotlin developers building applications that need SQL persistence, requery combines a typed query DSL with compile-time generation of entity and model code. It is open source and supports Android as well as JDBC-backed relational databases, making it relevant to teams that want generated typed entities rather than a general-purpose database administration tool. Its focus is implementation within an application, not a broad data platform.

The library’s feature set centers on mapping application models to relational data. It handles one-to-one, one-to-many, many-to-one, and many-to-many relationships, and includes caching, custom type converters, updates, and database-specific upsert generation. Query execution can be blocking or non-blocking, with optional RxJava Observable results. The listed SQL dialects are PostgreSQL, MySQL, Oracle, Microsoft SQL Server, SQLite, Apache Derby, H2, and HSQLDB; Android SQLite is also part of its stated scope. This breadth is useful for teams working across those databases, though the described offering remains specifically SQL-oriented.

Because requery is self-hosted and open source, there are no paid tiers to compare; teams should account for their own adoption and maintenance work. Support is community-based, and the repository README and linked wiki are dated, so teams prioritizing current documentation or formal support should weigh alternatives. Choose requery when generated entities, static typing, and Java or Kotlin integration match the application. It is less suitable for teams seeking a managed service, non-SQL storage, or a product with vendor-backed support.

requery pros and cons

  • Where it wins
    • Compile-time entity and model code generation
    • Typed query DSL maps directly to SQL
    • Blocking, non-blocking, and optional RxJava query APIs
  • Where it doesn't
    • Limited to Java, Kotlin, and Android application use
    • Database support centers on listed relational dialects
    • Community support; project documentation is dated

requery fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. How we rank.

Last updated · How we research and update