One query can wreck your database performance. Find out how I found this silent killer and sped up my apphttps://schneems.com/2017/07/18/how-i-reduced-my-db-server-load-by-80/ …
-
would that be generalizable? work better than trying to save and re-playing the validation in Ruby?
SQLite still only has the error message, and we don't have as much control over constraint names. I like your idea of replaying them
-
-
If we have the violated constraint name, maybe we could match the column by finding the constraint in INFORMATION_SCHEMA
-
One downside of that approach is if there's multiple failing fields, we don't know that, only the first failure. Our UI suffers.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.