[email protected] wrote: > well i'd like to thank everyone who's given me some responses. i've > looked at all the precooked solutions that were suggested but what it > really boils down to is i enjoy the programming challenge and i'm > still not convinced i need/want to switch all the data in my app to > someone elses app. it just isnt worth it for my needs.
Well, there is something to be said for not reinventing the wheel. On the other hand, if you can build a better wheel, do it! > > im going to look deeper into using serialize but what i really wanted > was the full abilities of rails for validations, callbacks, etc... You can have that in any Rails app. Serialization is not relevant to that. Now, it's true that serialization can be abused. You want to make sure that you separate fields as much as possible if you know that they're going to be separate. But it's great for dynamic user-defined attributes. > > in any event.. thanks for the input guys, it was much appreciated. > > - FJM Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://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.
