Re: storing start/end times
Posted by: Dimitris Papageorgiou
Date: April 08, 2015 07:59AM

Peter Brawley Wrote:
-------------------------------------------------------
> > only 7 rows(one for each weekday)...
>
> Looks like a design mistake.
Why a design mistake?
I assume what you propose is having 7 cols for each weekday...and rows the correspond to half-hour(or other) intervals...is the aforementioned what you propose?

> > there may be a case where the store/s be close
> at a specific date
>
> "May be"? It's virtually certain.
>
> > ...for that, I assume the user/store owner will
> just use the app and the day
> > to which the specific date corresponds will mark
> it as close.
>
> To deliberately build in such awkwardness also
> looks like a design mistake.

Maybe you are not wrong here.
> > How a stored procedure will help here
>
> To encapsulate the logic that builds a yearly
> calendar and all its specifics, eg identifying
> when Good Friday, Xmas and national holidays occur
> in a given year.

you said...yearly calendar...does that mean having 365 columns?

All-in-all...I am trying to figure out how this calendar table will be-its design/form..so I can begin SQL coding etc.

Options: ReplyQuote


Subject
Written By
Posted
Re: storing start/end times
April 08, 2015 07:59AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.