On Tue, Mar 17, 2009 at 10:56 AM, luxagraf <luxag...@gmail.com> 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 <dar...@afoyi.com> wrote: > > The first issue that comes to mind with that idea is what if the business > has > > multiple opening periods in a day, such as open in the morning, closed > over > > lunch and open in the afternoon again? > > There are a few edge cases like that (also what to do for > establishments where the kitchen closes at one time, but the bar > remains open a bit later), which I haven't solved yet. But in both > cases loosely related models seem like the way to go. > > cheers > Scott Gilbertson > luxag...@gmail > > > Well the nice thing about the foreign key method is that you can actually have more than one open and closing for a given day, you just need to play with that in Python. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
