On Wed, Oct 24, 2012 at 12:39 PM, Dave Aronson <googlegroups2d...@davearonson.com> wrote: > On Wed, Oct 24, 2012 at 1:00 PM, Kevin McCaughey <li...@ruby-forum.com> wrote: > >> As for the Bookings table, the reasoning behind this is in case there >> are multiple meetings going on in the same building, at the same time - >> there needs to be a way to differentiate them. If I simply use a room >> number, then we still have the issue of a many to many for >> Meeting<->Place. So, I thought that rather than just do a straight join >> table, I could logically separate the meetings into "bookings" (if that >> makes sense). >> >> I am looking at all this from the staff point of view - I want staff >> (Person) to be able to fill in a time-table for their weeks and someone >> else be able to view meetings happening (i.e. a manager has a look at >> what his staff are doing for the week, can look at any one member of >> staff at a given point of time to see where they should be, are they >> safe etc). >> >> As for keeping track of the rooms, I am not too worried about that. > > Hmmmm. I'm thinking that in order to minimize conflicts due to typos > (someone books the Smythe room, but the next clerk doesn't know it's > spelled that way, and books the Smith room), and simplify the Bookings > stuff, I'd probably:
I wonder if something like that couldn't be address with PostgreSQL and hstore where you store a null hstore hash that has common names NAME2=>NULL,NAME2=>NULL, since searching that is easy. -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
