It's kind of an annoying but common problem -- I've done things with Xyz instance delegating to the current XyzVersion instance, then you sort of get everything for free (or minimal cost). I reckon save the fancy solutions for when it gets annoying down the track...
(If there is a nifty solution, I'd be interested...) You could also wrap the guest fields in a composed_of and use that on both models, to avoid duplicated code. I'd just stick with the easy solution though, at this stage... On Thu, Jul 22, 2010 at 11:37, Scott Harvey <[email protected]> wrote: > Well currently there are only a few fields for a booking and a few for > a guest but this will definitely expand in the future. > > I think the easiest solution is going to be to save the data on the > Booking model and then give the user a checkbox if they want to update > the Guest model with any new data that is entered. I was hoping to > find something a bit slicker but this solution should work just fine. > > Thanks > Scott > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
