Hi there,

PR 12016 fixes stable fixture UUIDs on PostgreSQL [1] [2]. This seems to be 
the last hurdle for first-class UUID support in ActiveRecord.

I submitted the PR over a week ago and thought I'd send a friendly nudge. 
The Travis CI seems to segfault occassionally due to minitest issues [3], 
so the build should probably be restarted to get the green light.

Do let me know if there's anything more I can do to bring this to Rails 4.1 
-- and potentially backport it to Rails 4.0?

  [1] https://github.com/rails/rails/pull/12016
  [2] https://github.com/rails/rails/issues/11524
  [3] https://github.com/rails/rails/issues/12042

Kind regards,

Roderick

P.S. While there, PR 12012 fixes inconsistent :datetime and :timestamp 
behavior between PostgreSQL and MySQL. Like the PR above, it's eagerly been 
awaiting your feedback: https://github.com/rails/rails/pull/12012

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to