Prim and proper dates
Since Rails will automatially maintain "created_on" and/or "updated_on" fields if you create them in your database, most everyone adds them (by most everyone I mean myself and....well, no....just myself). Having these date fields is all fine and dandy but honestly,
Fri Nov 18 00:10:53 Mountain Standard Time 2005 (FNMST for short)
aint gonna cut it in today's ajaxed,web-two-dot-oh world. So, how do you make your dates look decent enough to be normal? Why with .strftime() of course. Say you have a created_on datetime field in your database and you're calling it in a view with a little
<%= book.created_on %>
action. Purty it up by adding strftime like so:
<%= book.created_on.strftime("%m-%d-%y") %>
I bet you already figured out what the m, d and y stand for. If not, for shame! Fret not though, you do have more options to choose from, here's a list I found in the Ruby documentation (in the help files actually)
Enjoy!
Fri Nov 18 00:10:53 Mountain Standard Time 2005 (FNMST for short)
aint gonna cut it in today's ajaxed,web-two-dot-oh world. So, how do you make your dates look decent enough to be normal? Why with .strftime() of course. Say you have a created_on datetime field in your database and you're calling it in a view with a little
<%= book.created_on %>
action. Purty it up by adding strftime like so:
<%= book.created_on.strftime("%m-%d-%y") %>
I bet you already figured out what the m, d and y stand for. If not, for shame! Fret not though, you do have more options to choose from, here's a list I found in the Ruby documentation (in the help files actually)
Time#strftime directives
|
Enjoy!
0 Comments:
Post a Comment
<< Home