this might be worth a look : http://codaset.com/codaset/codaset/blog/create-schema-less-dynamic-model-attributes
On Jan 7, 10:46 pm, Marnen Laibow-Koser <[email protected]> wrote: > [email protected] wrote: > > i guess what i meant to say was that if i created a user-defined > > column then i (through some magical UI controls which i'd eventually > > throw together) would like to be able to say is "this column is an > > integer.." and when i use that new user defined column it gets the > > full benefits of validates_numericality_of ... user_column_1.. what i > > was driving at was if i create a serialized column and create pseudo- > > fields inside of that then theres no way to get baked in validations > > and i'd end up creating my own validation functions. > > Not really true AFAIK. While I've never done this with serialized > fields, I don't believe Rails should have much trouble validating on > virtual or serialized attributes as if they were DB fields. > > > > > im sure this sort of thing is possible but im thinking its going to be > > a lot of trouble... hopefully nt more than its worth. > > I think you're anticipating more trouble than you'll actually have. > > > however, if i can invent a better wheel i'd love to share it with the > > world... so that kinda urges me to push forward. > > Good luck! > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > 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.
