If, in your application you are expecting value_a but it's either nil or
you have another value, that could be logger.error (if it's critical to the
continuation of the application) or if you can work around it but want to be
notified about it to sort it out in the future it could be logger.warn,
logger.info could be "I'm here #{value_a}"
Anyway, it's up to you to decide what is a warning and what is an error.
I just googled this for you ........
http://www.faqs.org/docs/evms/loglevels.html
On 16 March 2010 12:03, Tom Mac <[email protected]> wrote:
> Hi Colin
>
> Thanks for replying back. One more thing I need to clarify is when
> to use the different levels for logging? For example say in controller
> we can write
> logger.info "some thing" or logger.warn "something"
> How can we know that we should chose this here say info or warn
> here? Is there any criteria for this? My question may be blunder please
> excuse. Could you please pont to a good example?
>
> Tom
> --
> Posted via http://www.ruby-forum.com/.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<rubyonrails-talk%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-talk?hl=en.
>
>
--
100% naturally selected. 0% designed.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
