Hotfix for Rails bug with NaN integer column values

See rails/rails#8757 - After the 'rescue' truthiness check was removed from integer column casting in 3.2.9 (which itself was a bug causing incorrect default values from Flash NaNs), this bug appeared raising an exception when NaN.to_i is called.

The temporary fix is to convert all NaN to nil which is correctly interpreted by Rails. This is what they end up being anyway, since the database adapter will convert NaN to NULL in all cases I know of.
Cleaning the backtrace does squat, since we're *in* the framework.

So remove silencers, that might give us a useful log message and would have made debugging this issue a dozen times easier.
Merge pull request #1 from trisweb/master

Hotfix for Rails bug with NaN integer column values