Marnen Laibow-Koser wrote in post #975923: > Garrett Lancaster wrote in post #975922: >> Not sure if it's the best way, but here's an idea. For each custom form, >> use some combination of serialized db fields (one to hold the form >> meta-data (field-types, field names, etc.) and a corresponding field to >> hold the data. > > If you're using a relational database, I think it would actually be > better to have Form, Field, ValueSet, and Value models (and associated > tables):
Er, sorry. I changed ValueSet to Record and missed that instance. > > 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.
