Xavier Noria bbe7dac223 revert setting NOT NULL constraints in add_timestamps ...

Commit 3dbedd2 added NOT NULL constraints both to table
creation and modification. For creation the new default
makes sense, but the generic situation for changing a
table is that there exist records. Those records have
no creation or modification timestamps, and in the
general case you don't even know them, so when updating
a table these constraints are not going to work. See
a bug report for this use case in #3334.

2012-03-01 16:16:31 -08:00

..

active_record

revert setting NOT NULL constraints in add_timestamps

2012-03-01 16:16:31 -08:00

rails/generators

Tidy up migration types.

2011-12-24 10:52:45 +01:00

active_record.rb

Move DefaultScope and NamedScope under Scoping

2011-12-15 20:45:42 +00:00