Rails Console: reload! not reflecting changes in model files? What could be possible reason?

Question

Earlier it was working fine. I have been playing little bit config. So may be i have changed some config unknowingly.

here is config of environment/development.rb

  config.cache_classes = false

  # Log error messages when you accidentally call methods on nil.
  config.whiny_nils = true

  # Show full error reports and disable caching
  config.consider_all_requests_local       = true
  config.action_view.debug_rjs             = true
  config.action_controller.perform_caching = false

  # Don't care if the mailer can't send
  config.action_mailer.raise_delivery_errors = false

  # Print deprecation notices to the Rails logger
  config.active_support.deprecation = :log

  # Only use best-standards-support built into browsers
  config.action_dispatch.best_standards_support = :builtin

  # migration prefix with sequence #s
  config.active_record.timestamped_migrations = false

  #time zone
  config.time_zone = 'UTC'

Here is config section of application.rb

 # Configure the default encoding used in templates for Ruby 1.9.
 config.encoding = "utf-8"

 # Configure sensitive parameters which will be filtered from the log file.
 config.filter_parameters += [:password]

 config.active_record.schema_format = :sql

when i run reload! on rails console it return true

score 191 · Accepted Answer · edited Jul 29 '18 at 17:49

191

reload! only reloads the latest code in the console environment. It does not re-initialize existing objects.

This means if you have already instantiated any objects, their attributes would not be updated - including newly introduced validations. However, if you create a new object, its attributes (and also validations) will reflect the reloaded code. more here

edited Jul 29 '18 at 17:49

Rakib

12,376
16
77
113

answered Mar 25 '11 at 04:04

Nazar Hussain

5,102
6
40
67

What about custom validation? I have defined some methods and registered with validate. When i change validation logic, its not reflected on reload!. – Maddy.Shik Mar 25 '11 at 07:18
2

It will reflect when you re-initialize the object. – Nazar Hussain Mar 25 '11 at 08:48

score 21 · Answer 2 · answered Mar 25 '11 at 04:00

21

Are you reloading the object from the database?

For example:

>> a = User.last
=> #<User id: 16, email: "asdfadsf@sdfdsf.com">
>> reload!
Reloading...
=> true

'a' won't reflect any changes to your model until you reload it from the db.

answered Mar 25 '11 at 04:00

ctide

5,217
1
29
26

1

Note - this is true even when accessing a method on an object. Eg, if you change the definition of the class method foo(), then in the console a.foo will not use the new definition unless you first reload a. – jpw Jun 12 '13 at 00:29

Rails Console: reload! not reflecting changes in model files? What could be possible reason?

2 Answers2

Linked