Uploaded image for project: 'Mongoid'
  1. Mongoid
  2. MONGOID-1658

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

    • Type: Icon: Task Task
    • Resolution: Done
    • 2.4.4
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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 Unassigned
            Reporter:
            priyaaank priyaaank
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: