After a few days testing different scenarios, my guess is that TORQUE-84 needs to be completed and tested in order to fully support Limit/Offset in SQL server 2005.
Without the patch, offset seems to be unsupported: I need to have PageSize * MemoryPageLimit that cover total records, or some will be unread. With the patch applied, using LargeSelect.getNextResultsAvailable() will never end the reading process and some extra data will be read. I even tried to calculate total pages from volume of records and use LargeSelect.getPage(x), same thing... For now, I will put that on ice since I have a lot of other tasks to do ;-) I will keep an eye on this thread and on TORQUE-84 development progress. Thanks to all for your precious help, Regards, Yannick Thomas Vandahl-2 wrote: > > Scott Eade wrote: >> LargeSelect exists specifically so that you can read through a large >> number of records in chunks of size memoryPageLimit. > > If I understand Yannick correctly he has an issue with MS-SQL not > working correctly with LargeSelect. I remember some problems with the > native limit/offset support of MS-SQL which should have been fixed some > time ago. If the problem can be reproduced, it probably isn't fixed. So > I would recommend to provide some test case which fails and open a JIRA > issue. > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/LargeSelect-example---tf4605414.html#a13510951 Sent from the Apache DB - Torque Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
