[SERVER-10911] Add $currentDate update modifier Created: 25/Sep/13 Updated: 02/Aug/18 Resolved: 28/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
Add a new update modifier where the server will fill in the date/timestamp: Usage:
|
| Comments |
| Comment by gross [ 13/Apr/16 ] |
|
gianfranco@10gen.com, I looked through mongodb 2.6, 3.0 and 3.2 source code and found that new BSONTimestamp(0, 0) in document to insert works for all fields (not for 1st and 2nd as it was in older mongodb) and produces unique timestamp for each field. |
| Comment by gross [ 13/Apr/16 ] |
|
ivan@kinvey.com, at least in mongo 2.6 and 3.2 this timestamp is unique for mongod instance. I'm not sure if it's unique in replSet but think it should be. |
| Comment by Gianfranco Palumbo [ 28/Mar/14 ] |
|
Could this operator be implemented for inserts? |
| Comment by Ivan Stoyanov [ 05/Feb/14 ] |
|
Hi, how atomic or close to atomic is that operation? |
| Comment by auto [ 01/Oct/13 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |
| Comment by auto [ 27/Sep/13 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |