hi roger,
the following works for me. i use a set instead of a collection:
public void testOrderByJoined2()
{
Criteria crit = new Criteria();
QueryByCriteria q = QueryFactory.newQuery(Project.class, crit,
true);
q.addOrderByAscending("persons.lastname");
I'm using my custom SQL paging. i have two new properties limit, offset
in AbstractQueryImpl which i use in SqlQueryStatement class. the SQL
paging is working, but there is a problem if i reuse the same
QueryByCriteria object with different values for LIMIT, OFFSET
is there a way to turn off q
Hi,
Thanx for the confirmation.
Is it necessary to add the orderby column to the returned columns in the
resultset, when the orderby column is a column of a joined table? This
is what causes this behaviour. I personnaly do not think so, since for
instantiating the objects, it is not required to b
