Database exceptions should be pushed to the errors
Reported by Tillsc | August 12th, 2011 @ 05:24 AM
When an object is valid but the save fails the reason why this
happened is often missing. So with dm 1.1 I often had the following
scenario:
foo.valid? #=> true
foo.save #=> false
foo.errors #=> []
I think it would be a great improvement if the original error message dropped by the database adapter would be part of the errors hash. E.g.:
foo.valid? #=> true
foo.save #=> false
foo.errors #=> [:database => "Duplicate entry '0' for key 'bar'"]
Comments and changes to this ticket
-
-
Mark Lee March 16th, 2021 @ 02:21 AM
It’s a great section for software developers. Here we can learn the functionality and applications of the Database exceptions very quickly
cheap real diamond rings online . It’s good for students too for their academic projects. Also, we can discuss the errors or problems here. It’s fast and easy to work. -
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Johannes
Tillsc