Purpose of after_initialize in ActiveRecord?

rubyonrails-talk
1

You should use after_initialize or you might find yourself running into some weird errors.

2

protected

3

You should use after_initialize or you might find yourself running into some weird errors.

What kind of errors and why? Calling super before your own init code seems logically equivelent to a filter and is more simple/OO. If using good OO design principles breaks the framework (FYI, this hasn't bitten me) I'd argue the framework needs fixing. Either way, it's helpful to get an explanation so we all learn something rather than just sying "don't do that, it's bad."

Thanks,

pt.

4

See here