fix(Model): findOrCreate will now accurately throw an error when `defaults` valu…
…es trigger a unique error For cases where the primary `where` passed to findOrCreate does not trigger a unique error but the default values does the code would then attempt a find on the were resulting in the perceived impossible return value of [null, true]
Showing
with
54 additions
and
6 deletions
-
Please register or sign in to post a comment