Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Luis Correa d'Almeida
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,

Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Jon Leighton
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 Co

Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Aaron Patterson
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

Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Luis Correa d'Almeida
That did the trick. It's far from intuitive though - agree should probably be considered a bug. On Fri, Jul 8, 2011 at 6:56 PM, Ken Collins wrote: > > Just do this and it will work. > > class Post < ActiveRecord::Base >  set_primary_key :id > end > > This may seem odd, but what is likely happenin

Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Ken Collins
Just do this and it will work. class Post < ActiveRecord::Base set_primary_key :id end This may seem odd, but what is likely happening is that since the id column is the same name as the expected default and the type is now a string, it is failing to set things correctly or cast them appropr

Re: [Rails-core] Setting primary key value manually

2011-07-08 Thread Geoff Harcourt
I never knew what the proper practice was for this sort of thing. In scenarios where I had to ensure that a primary key was set to a number I specified, I always used a callback to modify the ID to match a facade attribute if it had been set. I'm sure that's wrong, but I could never figure out a m

[Rails-core] Setting primary key value manually

2011-07-08 Thread Luis Correa d'Almeida
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.n