Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 06c4a3e

Browse files
Merge 5.0 into 5.x (#3156)
2 parents dd69219 + 98474c3 commit 06c4a3e

File tree

2 files changed

+8
-6
lines changed

2 files changed

+8
-6
lines changed

‎docs/query-builder.txt‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -195,9 +195,10 @@ the value of the ``title`` field is ``"Back to the Future"``:
195195

196196
You can use the ``id`` alias in your queries to represent the
197197
``_id`` field in MongoDB documents, as shown in the preceding
198-
code. When you run a find operation using the query builder, {+odm-short+}
199-
automatically converts between ``id`` and ``_id``. This provides better
200-
compatibility with Laravel, as the framework assumes that each record has a
198+
code. When you use the query builder to run a find operation, the {+odm-short+}
199+
automatically converts between ``_id`` and ``id`` field names. In query results,
200+
the ``_id`` field is presented as ``id``. This provides better
201+
consistency with Laravel, as the framework assumes that each record has a
201202
primary key named ``id`` by default.
202203

203204
Because of this behavior, you cannot have two separate ``id`` and ``_id``

‎docs/upgrade.txt‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -115,9 +115,10 @@ This library version introduces the following breaking changes:
115115
date classes, applying the default timezone.
116116

117117
- ``id`` is an alias for the ``_id`` field in MongoDB documents, and the library
118-
automatically converts between ``id`` and ``_id`` when querying data. Because
119-
of this behavior, you cannot have two separate ``id`` and ``_id`` fields in your
120-
documents.
118+
automatically converts between ``id`` and ``_id`` when querying data. The query
119+
result object includes an ``id`` field to represent the document's ``_id`` field.
120+
Because of this behavior, you cannot have two separate ``id`` and ``_id`` fields
121+
in your documents.
121122

122123
- Removes support for the ``$collection`` property. The following code shows
123124
how to assign a MongoDB collection to a variable in your ``User`` class in

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /