Unique constraints didn't make the cut for RavenDB 4.0

added by DotNetKicks
10/11/2017 12:21:04 PM

1 Kicks, 337 Views

That, however, led to a different problem. The process of using a unique constraint would now broken into two distinct parts. First, we would verify that the value is indeed unique, then we would save the document.