This was introduced in 0.9.5.
Query[User] query = Ebean.createQuery(User.class);query.addWhere(Expr.eq("loggedBugs.duplicateOf", "12"));
... the issue being the the property "loggedBugs.duplicateOf" will require a join and this is normally detected and added. The bug is that this is not the case in 0.9.5.
If there is a explicit join on the query then the error does not appear...Aka: query.join("loggedBugs");
Stupid bug... all 'includes'/'joins' are tested in lower case... the bug was that loggedBugs was not converted to loggedbugs (lower case b). Ironically the idea of using all lower case was to reduce issues like this :).
Oh well, fixed in 0.9.5b.
Worth noting that I introduced this in version 0.9.5. The way that logical property names are converted to database column names was changed. The code is better but came with this bug :(
Home