Update test to suppourt multiple database concurrent updates #3939
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some database may have a different implementation on ensuring uniqueness in domainName. If there is concurrent updates with same domainName in SQL, only one update goes through but if unique is not supported by shared SQL database there might be case where all update can go through sequentially which is not a concern if we maintain the uniqueness over the domainName.
So, added and modified domain test to support these cases.