Re: best way to organize models that store businesses/hours?

On Tue, Mar 17, 2009 at 10:56 AM, luxagraf wrote: > > Alex- > > Thanks for the suggestions... the 14 fields is definitely an option, > but like you said it feels awkward and would make it hard to adapt > should things change down the road. > > Darryl - > > > Darryl Ross wrote: > > The first issu

Re: best way to organize models that store businesses/hours?

Alex- Thanks for the suggestions... the 14 fields is definitely an option, but like you said it feels awkward and would make it hard to adapt should things change down the road. Darryl - > Darryl Ross wrote: > The first issue that comes to mind with that idea is what if the business has > mult

Re: best way to organize models that store businesses/hours?

Alex Gaynor wrote: > I guess technically you could just have 14 fields on the mode(open and > close for each day of the week), which is fine since days of the week > are a static number of things but that felt bulky to me(though it's > probably more preformant). The first issue that comes to mind

Re: best way to organize models that store businesses/hours?

On Mon, Mar 16, 2009 at 11:26 PM, luxagraf wrote: > > Hello all- > > I'm working of a site that will store various business listings > (restaurants, bars, clubs etc) and then I'd like to also track the > hours each business is open... The ultimate goal being something like > lawrence.com's "open

best way to organize models that store businesses/hours?

Hello all- I'm working of a site that will store various business listings (restaurants, bars, clubs etc) and then I'd like to also track the hours each business is open... The ultimate goal being something like lawrence.com's "open now" feature and other time-related queries of that type. I'm tr