Rails: differences in db/schema.rb - null: false at created_at/updated_at columns

Question

Does anybody know why whenever I run rake db:migrate in my production environment, the schema.rb file is changed?

The differences are only on the created_at, update_at columns of all model tables:

-    t.datetime "created_at"
-    t.datetime "updated_at"
+    t.datetime "created_at",            null: false
+    t.datetime "updated_at",            null: false

I know that this is what it finds in the production db, but why were they created as null: false there and not in the development db too?

@okliv They were created with the exact same scripts (rails db migrations). Obviously the tables created on production are different on these columns but why? — Lazarus Lazaridis, Sep 09 '13 at 11:20
@claptimes it would be fun if not and grotori hid it from us =) but... — okliv, Sep 09 '13 at 12:00

score 3 · Accepted Answer · answered Oct 11 '13 at 08:30

I had the same thing on my dev machine. Running db:drop in production is not a wise idea, but what will fix the 'problem':

rake db:drop db:create db:migrate

My mysql version had changed since I first created the database with rails. The migrations still ran according to the old mysql version.

This is what probabaly happens at your production environment.

score 0 · Answer 2 · answered Sep 10 '13 at 08:08

0

Check your mysql version in production system and system where you used in development mode. There was a similar issue with default values.

Check this link : https://www.ruby-forum.com/topic/134121

answered Sep 10 '13 at 08:08

AshwinKumarS

1,303
10
13

can you paste your migration here ? – AshwinKumarS Sep 10 '13 at 11:31
Unfortunately, I can't. – Lazarus Lazaridis Sep 10 '13 at 11:38
Check this : http://stackoverflow.com/questions/2563297/why-is-rails-setting-null-false-on-all-my-columns-in-schema-rb?rq=1 Any use ? – AshwinKumarS Sep 10 '13 at 11:50

Rails: differences in db/schema.rb - null: false at created_at/updated_at columns

2 Answers2

Linked