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
@@ -162,9 +164,9 @@ public DBCursor hint( String indexName ){
162
164
}
163
165
164
166
/**
165
-
* Use snapshot mode for the query. Snapshot mode assures no duplicates are
166
-
* returned, or objects missed, which were present at both the start and end
167
-
* of the query's execution (if an object is new during the query, or deleted
167
+
* Use snapshot mode for the query. Snapshot mode assures no duplicates are
168
+
* returned, or objects missed, which were present at both the start and end
169
+
* of the query's execution (if an object is new during the query, or deleted
168
170
* during the query, it may or may not be returned, even with snapshot mode).
169
171
* Note that short query responses (less than 1MB) are always effectively snapshotted.
170
172
* Currently, snapshot mode may not be used with sorting or explicit hints.
@@ -223,14 +225,14 @@ else if (n < 0)
223
225
/**
224
226
* Limits the number of elements returned in one batch.
225
227
* A cursor typically fetches a batch of result objects and store them locally.
226
-
*
228
+
*
227
229
* If <tt>batchSize</tt> is positive, it represents the size of each batch of objects retrieved.
228
230
* It can be adjusted to optimize performance and limit data transfer.
229
-
*
231
+
*
230
232
* If <tt>batchSize</tt> is negative, it will limit of number objects returned, that fit within the max batch size limit (usually 4MB), and cursor will be closed.
231
233
* For example if <tt>batchSize</tt> is -10, then the server will return a maximum of 10 documents and as many as can fit in 4MB, then close the cursor.
232
234
* Note that this feature is different from limit() in that documents must fit within a maximum size, and it removes the need to send a request to close the cursor server-side.
233
-
*
235
+
*
234
236
* The batch size can be changed even after a cursor is iterated, in which case the setting will apply on the next batch retrieval.
235
237
*
236
238
* @param n the number of elements to return in a batch
@@ -240,7 +242,7 @@ public DBCursor batchSize( int n ){
240
242
// check for special case, used to have server bug with 1
241
243
if ( n == 1 )
242
244
n = 2;
243
-
245
+
244
246
if ( _it != null ) {
245
247
if (_itinstanceofDBApiLayer.Result)
246
248
((DBApiLayer.Result)_it).setBatchSize(n);
@@ -270,18 +272,18 @@ public DBCursor skip( int n ){
0 commit comments