MongoDB\Collection::find()
Definition
Parameters
$filter
: array|object- The filter criteria that specifies the documents to query.
$options
: arrayAn array specifying the desired options.
NameTypeDescriptionallowDiskUse
boolean
Enables writing to temporary files. When set to
true
, queries can write data to the_tmp
sub-directory in thedbPath
directory.allowPartialResults
boolean
For queries against a sharded collection, returns partial results from the
mongos
if some shards are unavailable instead of throwing an error.batchSize
integer
The number of documents to return in the first batch. Defaults to
101
. A batchSize of0
means that the cursor will be established, but no documents will be returned in the first batch.Unlike the previous wire protocol version, a batchSize of
1
for thefind
command does not close the cursor.codec
MongoDB\Codec\DocumentCodec
The codec to use for encoding or decoding documents. This option is mutually exclusive with the
typeMap
option.Defaults to the collection's codec. Inheritance for a default
codec
option takes precedence over that of thetypeMap
option.New in version 1.17.
collation
array|object
Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks. When specifying collation, the
locale
field is mandatory; all other collation fields are optional. For descriptions of the fields, see Collation Document.If the collation is unspecified but the collection has a default collation, the operation uses the collation specified for the collection. If no collation is specified for the collection or for the operation, MongoDB uses the simple binary comparison used in prior versions for string comparisons.
comment
mixed
Enables users to specify an arbitrary comment to help trace the operation through the database profiler, currentOp output, and logs.
The comment can be any valid BSON type since MongoDB 4.4. Earlier server versions only support string values.
cursorType
integer
Indicates the type of cursor to use.
cursorType
supports the following values:MongoDB\Operation\Find::NON_TAILABLE
(default)MongoDB\Operation\Find::TAILABLE
hint
string|array|object
The index to use. Specify either the index name as a string or the index key pattern as a document. If specified, then the query system will only consider plans using the hinted index.
New in version 1.2.
let
array|object
Map of parameter names and values. Values must be constant or closed expressions that do not reference document fields. Parameters can then be accessed as variables in an aggregate expression context (e.g.
$$var
).This is not supported for server versions prior to 5.0 and will result in an exception at execution time if used.
New in version 1.13.
limit
integer
The maximum number of documents to return. If unspecified, then defaults to no limit. A limit of
0
is equivalent to setting no limit.A negative limit is similar to a positive limit but closes the cursor after returning a single batch of results. As such, with a negative limit, if the limited result set does not fit into a single batch, the number of documents received will be less than the specified limit. By passing a negative limit, the client indicates to the server that it will not ask for a subsequent batch by using getMore.
max
array|object
The exclusive upper bound for a specific index.
New in version 1.2.
maxAwaitTimeMS
integer
Positive integer denoting the time limit in milliseconds for the server to block a getMore operation if no data is available. This option should only be used if cursorType is
TAILABLE_AWAIT
.New in version 1.2.
maxTimeMS
integer
The cumulative time limit in milliseconds for processing operations on the cursor. MongoDB aborts the operation at the earliest following interrupt point.
min
array|object
The inclusive lower bound for a specific index.
New in version 1.2.
noCursorTimeout
boolean
Prevents the server from timing out idle cursors after an inactivity period (10 minutes).
projection
array|object
The projection specification to determine which fields to include in the returned documents. See Project Fields to Return from Query and Projection Operators in the MongoDB manual.
readConcern
Read concern to use for the operation. Defaults to the collection's read concern.
It is not possible to specify a read concern for individual operations as part of a transaction. Instead, set the
readConcern
option when starting the transaction.readPreference
Read preference to use for the operation. Defaults to the collection's read preference.
returnKey
boolean
If true, returns only the index keys in the resulting documents.
New in version 1.2.
session
Client session to associate with the operation.
New in version 1.3.
showRecordId
boolean
Determines whether to return the record identifier for each document. If true, adds a field
$recordId
to the returned documents.New in version 1.2.
skip
integer
Number of documents to skip. Defaults to
0
.sort
array|object
The sort specification for the ordering of the results.
typeMap
array
The type map to apply to cursors, which determines how BSON documents are converted to PHP values. Defaults to the collection's type map.
Return Values
A MongoDB\Driver\Cursor object.
Errors/Exceptions
MongoDB\Exception\UnsupportedException
if options are used and
not supported by the selected server (e.g. collation
, readConcern
,
writeConcern
).
MongoDB\Exception\InvalidArgumentException
for errors related to
the parsing of parameters or options.
MongoDB\Driver\Exception\RuntimeException for other errors at the extension level (e.g. connection errors).
Behavior
When evaluating query criteria, MongoDB compares types and values according to its own comparison rules for BSON types, which differs from PHP's comparison and type juggling rules. When matching a special BSON type the query criteria should use the respective BSON class in the extension (e.g. use MongoDB\BSON\ObjectId to match an ObjectId).
Examples
The following example finds restaurants based on the cuisine
and borough
fields and uses a projection to limit the fields that are
returned. It also limits the results to 5 documents.
$collection = (new MongoDB\Client)->test->restaurants; $cursor = $collection->find( [ 'cuisine' => 'Italian', 'borough' => 'Manhattan', ], [ 'limit' => 5, 'projection' => [ 'name' => 1, 'borough' => 1, 'cuisine' => 1, ], ] ); foreach ($cursor as $restaurant) { var_dump($restaurant); };
The output would then resemble:
object(MongoDB\Model\BSONDocument)#10 (1) { ["storage":"ArrayObject":private]=> array(4) { ["_id"]=> object(MongoDB\BSON\ObjectId)#8 (1) { ["oid"]=> string(24) "576023c6b02fa9281da3f983" } ["borough"]=> string(9) "Manhattan" ["cuisine"]=> string(7) "Italian" ["name"]=> string(23) "Isle Of Capri Resturant" } } object(MongoDB\Model\BSONDocument)#13 (1) { ["storage":"ArrayObject":private]=> array(4) { ["_id"]=> object(MongoDB\BSON\ObjectId)#12 (1) { ["oid"]=> string(24) "576023c6b02fa9281da3f98d" } ["borough"]=> string(9) "Manhattan" ["cuisine"]=> string(7) "Italian" ["name"]=> string(18) "Marchis Restaurant" } } object(MongoDB\Model\BSONDocument)#8 (1) { ["storage":"ArrayObject":private]=> array(4) { ["_id"]=> object(MongoDB\BSON\ObjectId)#10 (1) { ["oid"]=> string(24) "576023c6b02fa9281da3f99b" } ["borough"]=> string(9) "Manhattan" ["cuisine"]=> string(7) "Italian" ["name"]=> string(19) "Forlinis Restaurant" } } object(MongoDB\Model\BSONDocument)#12 (1) { ["storage":"ArrayObject":private]=> array(4) { ["_id"]=> object(MongoDB\BSON\ObjectId)#13 (1) { ["oid"]=> string(24) "576023c6b02fa9281da3f9a8" } ["borough"]=> string(9) "Manhattan" ["cuisine"]=> string(7) "Italian" ["name"]=> string(22) "Angelo Of Mulberry St." } } object(MongoDB\Model\BSONDocument)#10 (1) { ["storage":"ArrayObject":private]=> array(4) { ["_id"]=> object(MongoDB\BSON\ObjectId)#8 (1) { ["oid"]=> string(24) "576023c6b02fa9281da3f9b4" } ["borough"]=> string(9) "Manhattan" ["cuisine"]=> string(7) "Italian" ["name"]=> string(16) "V & T Restaurant" } }
See Also
find command reference in the MongoDB manual