Looks like a good place to give this a spin: http://railscasts.com/episodes/121-non-active-record-model
Basically, use a pure-ruby class to wrap the location types and let it support an ActiveRecord like interface (mainly find and all). Then you can do collection_select the way you would with a normal ARec model. Depending on which version of Rails you're working with you may also check into PassiveRecord. It's a pretty advanced version of the same concept. Unfortunately it has dependencies on older versions of ARec. On Nov 5, 3:02 pm, James Byrne <[EMAIL PROTECTED]> wrote: > Frederick Cheung wrote: > > On Nov 5, 7:31 pm, James Byrne <[EMAIL PROTECTED]> > > wrote: > >> default_location_type = 'MAIN' > > > Personally I would have it as a constant of the Location class, ie > > > class Location ... > > VALID_TYPES = [...] > > end > > > Fred > > Point taken. > > Nonetheless, in the interim I have tested it and this does indeed work > as expected. However, I used private methods and public getters to > implement. > > def valid_location_type > virt_valid_type > end > > private > > def virt_valid_type > vvt = > [ > ['MAIN - Main Address', 'MAIN'], > ['POST - Postal Delivery', 'POST'], > ['DELV - Package Delivery', 'DELV'], > ['SHIP - Package Shipping', 'SHIP'], > ['OTHR - Other', 'OTHR'] > ] > end > > But my question remains: Is this the preferred idiom or is there > another recommended way to do this? > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
