yeah, I routed the engine in the main application routes as follows:
mount MyEngine::Engine => '/myengine'
and rake routes shows it as mounted as expected, it just doesnt
actually let you access it when running the server.
On Jul 7, 5:09 pm, Juan Manuel Barreneche
wrote:
> Hi!
>
>
>
> On Thu, J
ok so it's working (to a degree on edge rails):
all the build, install etc work as expected (even generators within
the engine folder).
however, the following does not work when in the app I want to mount:
rake railties:install:migrations
it doesn't copy the migrations over from the engine into
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
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
To clarify, I was previously doing using a callback via before_create,
like so
before_create :set_uuid
def set_uuid
self.id = UUIDTools::UUID.timestamp_create.to_s
end
On Jul 8, 6:45 pm, Geoff Harcourt wrote:
> I never knew what the proper practice was for this sort of
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
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
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
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
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,
10 matches
Mail list logo
