That's weird - MySQL 5.6 does support millisecond precision for date/time fields, according to the docs? You have to use the right format on your column definitions though.
> On 6/12/2014, at 10:19 , Paco Guzmán <pacoguzm...@gmail.com> wrote: > > Hi, > > In one app I'm working on we're using a MySQL 5.6 database and we're using a > belongs_to association with the touch option pointing to a datetime column on > other entity. > > But we noticed that we need more precision so we could invalidate properly a > cache key based on that column. > > I was thinking on a feature request so we can use an integer column instead a > datetime column (this MySQL doesn't store millisecond precision) to be > touched, we'll store in that column the current time with millisecond > precision. > > Would the core team consider this feature request? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscr...@googlegroups.com > <mailto:rubyonrails-core+unsubscr...@googlegroups.com>. > To post to this group, send email to rubyonrails-core@googlegroups.com > <mailto:rubyonrails-core@googlegroups.com>. > Visit this group at http://groups.google.com/group/rubyonrails-core > <http://groups.google.com/group/rubyonrails-core>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
