# Date-conventions

**URL:** <https://www.ruby-forum.com/t/date-conventions/163327>\
**Category:** Rails\
**Created:** [March 19, 2009, 10:11am UTC](https://www.ruby-forum.com/t/date-conventions/163327 "2009-03-19T10:11:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebastianj](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9fc348/32.png) [@sebastianj](https://www.ruby-forum.com/u/sebastianj)\
**Post date:** [March 19, 2009, 10:11am UTC](https://www.ruby-forum.com/t/date-conventions/163327/1 "2009-03-19T10:11:50Z")

</div>

hey all  
i got a (hopefully) simple question…

i want to name a datetype. now i started thinking about, if its

**purchased\_at**

or

**purchased\_on**?

its only a date and not a datetime…

ty  
Sebastian

---

<div class="post-metadata">

**Author:** ![sebastianj](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9fc348/32.png) [@sebastianj](https://www.ruby-forum.com/u/sebastianj)\
**Post date:** [March 19, 2009, 2:02pm UTC](https://www.ruby-forum.com/t/date-conventions/163327/2 "2009-03-19T14:02:30Z")

</div>

I’ve always followed:

\*\_on =\> some date  
\*\_at =\> some datetime

I rarely ever use date only fields though. Sure you don’t want to  
store the purchase date _and_ time? Up to you of course…

On Mar 19, 5:11 am, Sebastian Joecks \<rails-mailing-l…@andreas-