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
These exists a function Cursor::next() which accepts an optional argument wait, which may be a bool, None, or a number type.
cursor.next(wait=True) (default):
Wait indefinitely for the next row of the cursor.
cursor.next(wait=False), cursor.next(wait=None), cursor.next(wait=0):
No wait will be performed. If data is immediately available, it will be returned normally, or if data is not immediately available, RqlDriverError("Timed out waiting for cursor response.") will be raised.
If wait is any number greater than 0, the same behavior will occur except that we will wait up to wait seconds for data to become available before raising the RqlDriverError.
If the cursor is empty or completely exhausted and next is called, a StopIteration error will be raised.
In ruby:
There exists a function Cursor::next() which accepts an optional argument, which may be true, false, nil, or a number type.
cursor.next(true) (default):
Wait indefinitely for the next row of the cursor.
cursor.next(false), cursor.next(nil), cursor.next(0):
No wait will be performed. If data is immediately available, it will be returned normally, or if data is not immediately available, Timeout::Error("Timed out waiting for cursor response.") will be raised.
If the argument is any number greater than 0, the same behavior will occur except that we will wait up to that many seconds for data to become available before raising the Timeout::Error.
If the cursor is empty or completely exhausted and next is called, a StopIteration error will be raised.
See rethinkdb/rethinkdb#3529
@Tryneus can you briefly sum up the syntax of the option here and mention which terms are accepting it exactly?
The text was updated successfully, but these errors were encountered: