I've been using UUIDs since 3.0 stable and it works fine. Prior to 3.0 stable, there was code in activerecord that assumed an integer when assigning to id but that was fixed throughout 3.0.x. This seems to be a different issue, will log it as soon as I have minute.
On Fri, Jul 8, 2011 at 8:33 PM, Jon Leighton <[email protected]> wrote: > I tried using non-integer keys a while back and eventually gave up. I > half got it working, but there were numerous issues. This is something > I'd really like to get working properly in 3.2. > > On Fri, 2011-07-08 at 12:02 -0700, Aaron Patterson wrote: >> On Fri, Jul 08, 2011 at 10:37:50AM -0700, Luis Correa d'Almeida wrote: >> > In ActiveRecord 3.1.0.rc4, setting the id manually no longer works - >> > the assignment seems to be ignored. Is this expected behavior? Seems >> > to break BC >> > >> > create_table :posts, :id => false do |t| >> > t.string :id, :limit => 36, :primary => true, :null => false >> > t.string :title >> > end >> > >> > > @post = Post.new >> > > @post.id = "abc123" >> > > @post.id >> > => nil >> > >> > > @post.save! >> > => Fails because id is nil/null (obviously) >> > >> > Thoughts? >> >> If it worked in 3.0.9, but doesn't work in 3.1.0, please file a ticket >> (along with a test case if you can). In this case, I think it's likely >> this behavior was undefined (had no test case). At the very least we >> should add a test case that specs the behavior for this. >> > > -- > http://jonathanleighton.com/ > -- Luis Corrêa d'Almeida tribe.fm/luis -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
