I'm a bit confused and can't find the JPA version that uses longs instead of
ints as mentioned in the migration guide at:
https://cwiki.apache.org/WICKET/migration-to-wicket-60.html
Repeaters
* `IDataProvider` was converted to using `long` instead of `int` to
better line up with JPA and
4.8.4 Aggregate Functions in the SELECT Clause The result of a query
...
The Java type that is contained in the result of a query using an
aggregate function is as follows:
COUNT returns Long.
...
-igor
On Fri, May 3, 2013 at 8:35 AM, Paul Bors p...@bors.ws wrote:
I'm a bit confused and can't
?
Or am I missing something?
~ Thank you,
Paul Bors
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Friday, May 03, 2013 11:45 AM
To: users@wicket.apache.org
Subject: Re: Wicket 6.x and Repeaters API change to use longs
4.8.4 Aggregate Functions in the SELECT
: Re: Wicket 6.x and Repeaters API change to use longs
4.8.4 Aggregate Functions in the SELECT Clause The result of a query ...
The Java type that is contained in the result of a query using an aggregate
function is as follows:
COUNT returns Long.
...
-igor
On Fri, May 3, 2013 at 8:35 AM
Subject: Re: Wicket 6.x and Repeaters API change to use longs
yes. when i was looking at this i thought about making the dataprovider
paging param ints, but then the long return type didnt make sense.
since count() returns a long its feasible to request offsets in the long
range - eg user presses
