Result — Documentation by YARD 0.9.37 (original) (raw)

Class: Mongo::Operation::Indexes::Result

Inherits:

Result

• Object
• Result
• Mongo::Operation::Indexes::Result show all

Defined in:

lib/mongo/operation/indexes/result.rb

Overview

Defines custom behavior of results when using the listIndexes command.

Constant Summary

Constants inherited from Result

Result::CURSOR, Result::CURSOR_ID, Result::FIRST_BATCH, Result::N, Result::NAMESPACE, Result::NEXT_BATCH, Result::OK, Result::RESULT

Instance Attribute Summary

Attributes inherited from Result

#connection, #connection_description, #connection_global_id, #context, #replies

Instance Method Summarycollapse

• #cursor_id ⇒ Integer private
  Get the cursor id for the result.
• #documents ⇒ ArrayBSON::Document
  Get the documents for the listIndexes result.
• #namespace ⇒ String private
  Get the namespace for the cursor.
• #validate! ⇒ Result private
  Validate the result.

Methods inherited from Result

#acknowledged?, #cluster_time, #each, #error, #has_cursor_id?, #initialize, #inspect, #labels, #ok?, #operation_time, #reply, #returned_count, #snapshot_timestamp, #successful?, #topology_version, #write_concern_error?, #written_count

Instance Method Details

#cursor_id ⇒ Integer

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.

Note:

Even though the wire protocol has a cursor_id field for all messages of type reply, it is always zero when using the listIndexes command and must be retrieved from the cursor document itself.

Get the cursor id for the result.

#documents ⇒ ArrayBSON::Document

Get the documents for the listIndexes result. This is the ‘firstBatch’ field in the ‘cursor’ field of the first document returned.

#namespace ⇒ String

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.

Get the namespace for the cursor.

#validate! ⇒ Result

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.

Validate the result. In the case where the database or collection does not exist on the server we will get an error, and it’s better to raise a meaningful exception here than the ambiguous one when the error occurs.