diff options
author | Chris Arcand <chris@chrisarcand.com> | 2016-03-23 08:39:26 -0400 |
---|---|---|
committer | Chris Arcand <chris@chrisarcand.com> | 2016-03-24 13:17:14 -0400 |
commit | 16dadb1223fcabc9d904456d4b64d6e82f9e1a76 (patch) | |
tree | 95a869da996d916463911200affb17a4caf52eae /activerecord/test/cases/store_test.rb | |
parent | 2e8a350c38715787ab79603bf1e4b6296e23d80b (diff) | |
download | rails-16dadb1223fcabc9d904456d4b64d6e82f9e1a76.tar.gz rails-16dadb1223fcabc9d904456d4b64d6e82f9e1a76.tar.bz2 rails-16dadb1223fcabc9d904456d4b64d6e82f9e1a76.zip |
Make 'migrate' clear the schema cache afterward
Without clearing the caches afterward, removals done in migrations would
not be reflected in a separate task in the same process. That is, given
a table with a migration to remove a column, the schema cache would
still reflect that a table has that in something such as the
'db:seed' task:
`rake db:migrate db:seed`
(A common thing to do in a script for a project ala `bin/setup`)
vs
`rake db:migrate && rake db:seed`
(Two processes)
The first would not reflect that the column was removed.
The second would (cache reset).
Diffstat (limited to 'activerecord/test/cases/store_test.rb')
0 files changed, 0 insertions, 0 deletions