DOCSP-41335: Id field alias #3042
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ongodb into DOCSP-41335-id-alias
rustagir
approved these changes
Jul 15, 2024
docs/query-builder.txt
Outdated
Comment on lines
179
to
181
| ``movies`` collection that either match the ``_id`` | ||
| value of ``ObjectId('573a1398f29313caabce9682')`` or match | ||
| the ``title`` value ``"Back to the Future"``: |
There was a problem hiding this comment.
Suggested change
| ``movies`` collection that either match the ``_id`` | |
| value of ``ObjectId('573a1398f29313caabce9682')`` or match | |
| the ``title`` value ``"Back to the Future"``: | |
| ``movies`` collection in which the value of the``_id`` | |
| field is ``ObjectId('573a1398f29313caabce9682')`` or | |
| the value of the ``title`` field is ``"Back to the Future"``: |
docs/query-builder.txt
Outdated
Comment on lines
189
to
195
| .. note:: | ||
|
|
||
| Beginning in {+odm-short+} v5.0, you can use the ``id`` alias to | ||
| represent the ``_id`` field, as shown in the preceding code. When you | ||
| run a find operation using the query builder, {+odm-short+} | ||
| automatically converts between ``id`` and ``_id``. You cannot have | ||
| two separate ``id`` and ``_id`` fields in your documents. |
There was a problem hiding this comment.
S: (applies when you change the target branch to 5.0) Remove versioning since this is only going to be in that version of docs anyways
Suggested change
| .. note:: | |
| Beginning in {+odm-short+} v5.0, you can use the ``id`` alias to | |
| represent the ``_id`` field, as shown in the preceding code. When you | |
| run a find operation using the query builder, {+odm-short+} | |
| automatically converts between ``id`` and ``_id``. You cannot have | |
| two separate ``id`` and ``_id`` fields in your documents. | |
| .. note:: | |
| You can use the ``id`` alias in your queries to | |
| represent the ``_id`` field in MongoDB documents, as shown in the preceding code. When you | |
| run a find operation using the query builder, {+odm-short+} | |
| automatically converts between ``id`` and ``_id``. Because of this behavior, | |
| you cannot have two separate ``id`` and ``_id`` fields in your documents. |
rustagir
approved these changes
Jul 17, 2024
rustagir
force-pushed
the
DOCSP-41335-id-alias
branch
from
06e4c46
to
789621c
Compare
rustagir
force-pushed
the
DOCSP-41335-id-alias
branch
from
789621c
to
00e882d
Compare
|
Setting the Model laravel-mongodb/docs/eloquent-models/model-class.txt Lines 300 to 301 in ce05d9d |
GromNaN
approved these changes
Sep 5, 2024
| @@ -62,8 +63,8 @@ public function testOrWhere(): void | |||
| { | |||
| // begin query orWhere | |||
| $result = DB::connection('mongodb') | |||
| ->table('movies') | |||
| ->where('year', 1955) | |||
| ->collection('movies') | |||
There was a problem hiding this comment.
Suggested change
| ->collection('movies') | |
| ->table('movies') |
There was a problem hiding this comment.
I'll make the rest of these collection -> table changes in https://jira.mongodb.org/browse/DOCSP-42956
docs/query-builder.txt
Outdated
| ``_id`` field in MongoDB documents, as shown in the preceding | ||
| code. When you run a find operation using the query builder, {+odm-short+} | ||
| automatically converts between ``id`` and ``_id``. Because of this behavior, | ||
| you cannot have two separate ``id`` and ``_id`` fields in your documents. |
There was a problem hiding this comment.
We can explain that this behavior allows better compatibility with Laravel, "id" being the default name for primary keys in SQL databases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA - https://jira.mongodb.org/browse/DOCSP-41335
Staging - https://preview-mongodbnorareidy.gatsbyjs.io/laravel/DOCSP-41335-id/query-builder/#logical-or-example
Checklist