Rails - Jan 2006 - Migrations for populating authority tables

I''ve got a number of fixtures which populate
''authority'' tables in an
app (eg tables which are used to construct the values of selects or 
valid ''constants''). These will be updated infrequently and are
''configuration'' data, so I''m not sure its worth
constructing an
interface to do this in the deployed app.
Seeing as migrations can execute arbitrary code, I had thought of adding 
one to populate these authority tables-any thoughts on this approach?

-- 
Posted via http://www.ruby-forum.com/.

Sounds perfectly reasonable to me.

--  
-- Tom Mornini


On Jan 25, 2006, at 1:20 AM, Steve Lloyd wrote:
> I''ve got a number of fixtures which populate
''authority'' tables in an
> app (eg tables which are used to construct the values of selects or
> valid ''constants''). These will be updated infrequently
and are
> ''configuration'' data, so I''m not sure its worth
constructing an
> interface to do this in the deployed app.
> Seeing as migrations can execute arbitrary code, I had thought of  
> adding
> one to populate these authority tables-any thoughts on this approach?
>
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails