[Rake-devel] Can we make the rake class names more unique?

[Bennett, Patrick]

If you ask me, Rails is the one at fault here.  Since Rails can generate class names for tables that can have *any* name, it should ensure they're in an appropriately 'safe' namespace.

--- Original Message ---
From: "felkinator-ror at yahoo.com" <felkinator-ror at yahoo.com>
Sent: Sun 8/21/2005 10:37 am
To: "rake-devel at rubyforge.org" <rake-devel at rubyforge.org>
Subject: [Rake-devel] Can we make the rake class names more unique?

I'm working with rails and trying to use migrations
with my app. One of the tables I need to migrate
happens to be named 'Task'. I spent a couple hours
yesterday trying to get my migration to work, which
was just a minor variation on the example from the
documentation. It appears the reason is a name space
collision -- I was expecting an 'ActiveRecord' Task,
but I was getting the Rake Task. 

How about changing Task to RakeTask, or RkTask, or
something like that? How about adding a prefix to all
rake internal classes? Is there another better
solution?

-Kelly

------------------
http://www.kellyfelkins.org/
_______________________________________________
Rake-devel mailing list
Rake-devel at rubyforge.org
http://rubyforge.org/mailman/listinfo/rake-devel