What would make the most sense for the users? Do they need to be able to book under different names at different places?
(As for historical stuff, that's a bit different; you're always going to have duplication issues if you want to keep old information in the system.) How many fields are on the booking? On Thu, Jul 22, 2010 at 11:26, Scott Harvey <[email protected]> wrote: > That is sort of the path I was going down where I would have a guest > and each time a guest created a new booking the details about that > guest would be copied over to a BookingGuest (Stay) model. > > The question then came up as to when I should update the original > Guest model. Should the Guest model be updated every time an > associated BookingGuest model is updated? or would it be best to allow > the user to tick a checkbox if they want the original Guest model to > be updated, eg. "permanently update this guest?" > > Alternatively instead of having the BookingGuest model I could just > put all the fields on the Booking model but it seemed a bit message > having booking.guest_first_name, booking.guest_phone etc. > > -- > 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.
