Adding timestamp column causes stacktrace

If you use model/update to add a timestamp field to an existing model, and that existing model has data instances (ie. rows in its table), it will explode with a stacktrace complaining about non-nulls.   It seems that timestamp columns are created with a NOT NULL qualifier but no default, so any existing rows would have NULLs.
