[SERVER-938] Updates should not be allowed to modify the shard key Created: 19/Jan/10 Updated: 12/Jul/16 Resolved: 22/Apr/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
nothing we can do serverside for save-style updates. ORM-like libs should try to include the original shardkey in the query portion if possible of a save-style update. |
| Comments |
| Comment by Mathias Stearn [ 22/Apr/10 ] |
|
Looks like I typoed on the git commit for this: http://github.com/mongodb/mongo/commit/c4299e6c31b2e5e83611813d6ef66343f775458a |