Skip to content

Mention Ebean's query beans and their limitations with Play Ebean #919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mkurz merged 1 commit into from
Oct 9, 2026
+2 −0
Merged

Mention Ebean's query beans and their limitations with Play Ebean #919

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/manual/working/javaGuide/main/sql/JavaEbean.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,8 @@ As you can see, we've added a `find` static field, defining a `Finder` for an en

@[operations](code/javaguide/ebean/JavaEbeanTest.java)

> **Note:** Ebean also provides [query beans](https://ebean.io/docs/query/query-beans) for type-safe queries. Play Ebean doesn't set up their generation, and only enhances the code that uses them if it's in the packages of your models. You can set that up yourself, but it has limitations with incremental compilation, e.g. with sbt 1, queries using outdated query beans can compile and then fail at runtime. See [this comment on issue #61](https://github.com/playframework/play-ebean/issues/61#issuecomment-6089771595) for the configuration it needs, the versions it was tested with, and when to do a clean build.

## Transactional actions

By default Ebean will use transactions. However these transactions will be created before and committed or rollbacked after every single query, update, create or delete, as you can see here:
Expand Down