[SERVER-22] Feature-Req: index-based constraints and field "mutators" Created: 18/Apr/09 Updated: 03/Dec/15 Resolved: 03/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Jim Jones | Assignee: | David Storch |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
In addition to the much needed unique constraint, various other index-based constraints and "mutators" (for the lack of a better term) would be helpful. Ideas for Constraints: unique == field on inserted element must be unique "Mutators" would be things like: auto_increment == field on inserted element auto increments to MAX_VALUE+1 Feel free to edit this text if there's a better, established term for what I called "mutators" here. |
| Comments |
| Comment by David Storch [ 03/Dec/15 ] |
Closing as Won't Fix. |
| Comment by Aaron Staple [ 29/May/09 ] |
|
We have implemented the key uniqueness constraint ( |