From: "drbrain (Eric Hodel)" Date: 2013-03-16T09:37:54+09:00 Subject: [ruby-core:53471] [CommonRuby - Feature #8096] introduce Time.current_timestamp Issue #8096 has been updated by drbrain (Eric Hodel). Both Postgres and MySQL store timestamps with microsecond precision: http://www.postgresql.org/docs/9.2/static/datatype-datetime.html http://dev.mysql.com/doc/refman/5.6/en/datetime.html ---------------------------------------- Feature #8096: introduce Time.current_timestamp https://bugs.ruby-lang.org/issues/8096#change-37653 Author: vipulnsward (Vipul Amler) Status: Feedback Priority: Low Assignee: Category: Target version: =begin A lot of scenarios and applications require the use of (({Time.now.to_i})) which is used as current_timestamp in systems. The introduction of (({Time.current_timestamp})) {or something with similar with different name} would provide implicit integer timestamp instead of going from (({Time.now})) -> time_object -> to_i -> integer timestamp value So instead of Time.now.to_i # Outputs => 1363274618 one could use Time.current_timestamp # Outputs => 1363274618 =end -- http://bugs.ruby-lang.org/