Re: storing start/end times

[Dimitris Papageorgiou]

Peter Brawley Wrote:
-------------------------------------------------------
> > we just need day names here.
>
> Yikes no, eg Friday is a likely day with regular
> weekday open hours, but on Fri 3 Apr 2015 2015
> some stores may close at noon, and on Fri 25 Dec
> 2015 and Fri 1 Jan 2016 most stores may close
> altogether. You need a row for each day, and
> perhaps a stored procedure that writes the yearly
> calendar depending on such things.
>
> Database programming is a commitment to endless
> detail :-).

There are some things I do not understand...and are important.

Since we are going to have only 7 rows(one for each weekday)...how is it possible that the DATE stored in there varies(as it is suggested)?

you also mention that there may be a case where the store/s be close at a specific date...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.

This 3rd Q is related to the first one.How a stored procedure will help here...I have not quite understand this.