Rails core - Nov 2010 - Arel 2 isn't playing nice with my legacy tables

Specifically, it''s not playing nice with any type that it
doesn''t recognize,
eg. SET, ENUM, etc..

Just trying to start my Rails 3.0.2 app I get a NotImplementedError
exception "Column type `` is not currently handled" on the first SET
field
it encounters.

Am I missing something here?  Should I be disabling Arel for legacy tables
or something?

Thanks,
Jason

-- 
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.

Fixed in 2.0.3 - thanks.

On Mon, Nov 15, 2010 at 3:38 PM, Jason King <jk@handle.it> wrote:
> Specifically, it''s not playing nice with any type that it
doesn''t
> recognize, eg. SET, ENUM, etc..
>
> Just trying to start my Rails 3.0.2 app I get a NotImplementedError
> exception "Column type `` is not currently handled" on the first
SET field
> it encounters.
>
> Am I missing something here?  Should I be disabling Arel for legacy tables
> or something?
>
> Thanks,
> Jason
>
>
-- 
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.