Ah the wonders of the JPA never amaze me. Martijn
On 3/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
well given the above and the fact that idataprovider is mostly about paging i dont think this refactor is needed at this time until they fix those two ints. now given that this is jpa and the said methods are in an interface we can expect that fix to happen in a few months after never. so, i guess forget about this whole idea for now. -igor On 3/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > ok i am having a serious wtf moment > > so count queries in jpa now return a long instead of int > > but > > public Query setMaxResults(int maxResult); > public Query setFirstResult(int startPosition); > > so wtf? you can return a huge count but you cant page over the query? > > -igor > > > On 3/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > so i think this very simple refactor gout a bit out of control. see > > attached patches. thoughts? > > > > -igor > > > > > > On 3/19/07, Igor Vaynberg < [EMAIL PROTECTED]> wrote: > > > > > > hibernate 3.2 has switched from using an int to a long for returntype > > > of their count queries. jpa also uses a long. so i figure its time to > > > switch idataprovider to the long as well so that it maps nicely. since > > > we have broken 1.3 already, we might as well do it now. > > > > > > -igor > > > > > > > > > >
-- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
