This is to reflect when microrm can tell that a database constraint error has occurred, for easier error recovery. Otherwise, without significant effort, any consumer of microrm basically handles all errors, from "I/O error while accessing database file" to "database busy" to "constraint violation because you tried to associate two items that are already associated" very similarly.
This is to reflect when `microrm` can tell that a database constraint error has occurred, for easier error recovery. Otherwise, without significant effort, any consumer of `microrm` basically handles all errors, from "I/O error while accessing database file" to "database busy" to "constraint violation because you tried to associate two items that are already associated" very similarly.
This is to reflect when
micrormcan tell that a database constraint error has occurred, for easier error recovery. Otherwise, without significant effort, any consumer ofmicrormbasically handles all errors, from "I/O error while accessing database file" to "database busy" to "constraint violation because you tried to associate two items that are already associated" very similarly.Initial
ConstraintViolationsupport implemented.