MONGOID-1657 Don't hit database for uniqueness validation if BOTH scope and attribute hasn't changed.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • 2.4.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently uniqueness constraint is violated, if attribute on a mongoid document hasn't changed but scope has. To ensure that it doesn't happen, we need to make sure that scope reference hasn't changed either. Making a fix to check that. Submitting a pull request to fix newly opened bug MONGOID-1657.

              Assignee:
              Unassigned
              Reporter:
              priyaaank
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: