It seems that ActiveRecord cannot return sane errors when some constraint on a database operation is not met, for instance if you forget to set an attribute which has a “NOT NULL” constraint. If this happens AR simply throws an InvalidStatement exception. You would have to actually search your database logs for the error message. This really sucks! Also check out this blog post on the same topic. Oh well, perhaps I should try and fix this issue instead of griping, it’s open source after all. You can of course also argue that the model file in the Rails app was not complete (:allow_nil => false)..
-
Archives
- July 2011
- July 2010
- April 2010
- July 2009
- June 2009
- February 2009
- January 2009
- November 2008
- October 2008
- July 2008
- June 2008
- May 2008
- April 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- May 2007
- April 2007
- December 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
-
Meta