Permit $rename with a source that is a prefix of the destination or vice versa

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying, Write Ops
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current implementation of $rename prohibits any rename where the source and destination are along the same path: e.g., {$rename: {'a':'a.b'}} or {$rename: {'a.b':'a'}}. There is a TODO noting that it would be possible to relax this restriction.

      If we do want to make that change, now would be a good time, as we are making backwards-incompatible changes to update functionality.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: