Marnen Laibow-Koser wrote: > * Put the "extra" fields in some other table and use associations.
You *could* implement a simple "key - key value" model, and tie that back to the record and list since it seems that you'll have different custom fields per list. Perhaps the "list" model has an associated list of custom field definitions (name, type, size, etc?) Each "record" for the list finds out what its list's custom fields are, then maintains values for those in its associated table of 'custom field values' Or something like that... -- 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.
