OK I checked it manually in my workspace then. It looks good to me, so I'll commit to master and the 4.0.x branch. Thank you for the contribution Gagan!
2014/1/22 Gagan Juneja <[email protected]> > Hi Kasper, > I am not able to register with reviews repository. It is giving me below > error. > > Something broke! (Error 500) > > It appears something broke when you tried to go to here. This is > either a bug in Review Board or a server configuration error. Please > report this to your administrator. > > > Regards, > Gagan > > On Tue, Jan 21, 2014 at 3:54 PM, Kasper Sørensen (JIRA) <[email protected]> > wrote: > > > > [ > https://issues.apache.org/jira/browse/METAMODEL-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877368#comment-13877368] > > > > Kasper Sørensen commented on METAMODEL-35: > > ------------------------------------------ > > > > Hi Gagan, > > > > Can you please post your patch here: > https://reviews.apache.org/groups/metamodel/ > > > > (You can self register on that site). > > > >> DB2 query with limit returns random order results > >> ------------------------------------------------- > >> > >> Key: METAMODEL-35 > >> URL: https://issues.apache.org/jira/browse/METAMODEL-35 > >> Project: Metamodel > >> Issue Type: Bug > >> Reporter: Gagan Deep Juneja > >> Attachments: > 0001-Added-order-by-clause-to-the-RowNumber-Over-function.patch > >> > >> > >> I am using metamodel with DB2 database. I have one query where I want > >> to fetch records out of database with firstRow and MaxRow clauses. > >> What I found is this query doesn't work as expected and returns > >> duplicate records in different pages/batches. > >> I looked into the DB2QueryRewriter.java class and found that we are > >> using ROW_NUMBER() OVER() function in inner query to define order but > >> this is not working correctly, If I change this function call to > >> include order by clause on table Id field (ROW_NUMBER() OVER(order by > >> id)every thing works perfectly fine. > >> Please provide your valuable inputs on how to fix this for DB2 database. > >> We are using 3.4.7 version of metatmodel. > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.1.5#6160) >
