You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For SELECT queries with large number of result rows, it is nice to have an application level NyQLResult iterator. Like below.
// additional second parameter, 50, means we expect result 50 rows per page.Iterator<NyQLResult> paginator = nyqlInstance.paginate('script/path', 50, data).iterator();
while (paginator.hasNext()) {
// this result has 50 rows unless it is the last page in the whole result setNyQLResultpage = paginator.next();
// do something with result...
}
NOTE: This method will NOT manipulate database cursors. But we use JDBC setFetchSize() to efficiently fetch limited number of records to the memory at once, rather bringing all result rows into application memory. Each fetched rows will be returned to user for processing and then only loads the next block of rows.
The text was updated successfully, but these errors were encountered:
For SELECT queries with large number of result rows, it is nice to have an application level
NyQLResult
iterator. Like below.NOTE: This method will NOT manipulate database cursors. But we use JDBC
setFetchSize()
to efficiently fetch limited number of records to the memory at once, rather bringing all result rows into application memory. Each fetched rows will be returned to user for processing and then only loads the next block of rows.The text was updated successfully, but these errors were encountered: