@Tom, I'm a little surprised partial updates are on by default in new 2.1 projects as well. Your idea of being able to change this setting on a case by case basis makes sense.I look at it as more of a performance improvement which can be applied if you have a model with BLOBs or index columns.Rails keeps a list of which attributes are “dirty” and only updates those when you call Active Record#save.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
I was absolutely clueless this was happening (I stupidly upgraded to 2.1 on a whim, thinking that I hadn’t written any significant code yet so incompatibilities wouldn’t bother me — true enough, the only incompatibility was with my mental model of how Active Record worked), but I successfully diagnosed the — a dirty bit wasn’t getting set for the serialized object.
OK, no problem, the same thing happens at the day job with our Java system — which means I can use the same hacky solution to the problem.
I have wondered over and over how Rails can have so many useful features...
In my edit form I simply cannot figure out why collection_select isn’t saving the various values when it's nested. Needing to create/update new Race Events(join Model) for each Race. On the collection_select it’s not necessary and important not to include the object directly.