Skip to content

Conversation

@bukkasamudram
Copy link

@bukkasamudram bukkasamudram commented Feb 28, 2017

As per my understanding, If the application can tolerate non-atomic updates for two pieces of data, you can store these data in separate collections.


This change is Reviewable

As per my understanding, If the application can tolerate non-atomic updates for two pieces of data, you can store these data in separate collections.
@kay-kim
Copy link
Contributor

kay-kim commented Jul 17, 2019

Hi. Thank you for this pull request and apologies for the long delay.

While your statement is true, in context of the paragraph, I do believe that "separate documents" is appropriate (the separate documents can be in the same or different collections). As such, I will close this pull request. However, we greatly appreciate your time and effort to improve the docs. And apologies once again for the lateness of the response.

Regards,

Kay Kim

@kay-kim kay-kim closed this Jul 17, 2019
mongo-cr-bot pushed a commit that referenced this pull request Mar 30, 2023
* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 ObjectId in mongosh server updates

* DOCSP-28696 mongosh updates for server ticket

* Review feedback

* Staging fixes

* Staging fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants