Seriously when faced with dates as an issue the best
solution is to create a diary type database of dates.
This should always include audit trcaking for entrys.
Time and hence dates mesns money as they say so it
makes sense to control this as a resource.
Even if you include every date in the year for a
decade this will be under 4k of records. But as a
resource it will repay over and over again.
Ever site should have one and use it as the master
against all apps.
I don't see data and apps in isolation. Data is a core
product reused over many apps. Part of our work as
designers and developers is the reuse of corporate
data as a resource. The database of dates falls into
this category as an essential core resource within the
In the diary database goes everthing that might be
appropriate for the area. from school holidays to
Office parties etc..
The database should included audit tracking and access
should be strictly controlled.
Compliments of the season to all.
--- Ken Schaefer <ken@a...> wrote:
> Could be tricky(ish) - what about public holidays
> ----- Original Message -----
> From: "Roland Boorman" <r_boorman@y...>
> To: "sql language" <sql_language@p...>
> Sent: Friday, December 15, 2000 11:57 PM
> Subject: [sql_language] Re: Counting working days
> > why not datedif whole week then minus (datedif sat
> > datedif sun)
> > --- David Taylor <dtaylor@d...>
> > > How do you count the number of working days
> > > two dates? DATEDIFF has
> > > the weekday parameter, but it still runs from
> sun to
> > > sat.
> > >
> > > I think DATEDIFF(D1,D2,2) + DATEDIFF(D1,D2,3)
> > > +,...,DATEDIFF(D1,D2,6) would
> > > work, but it's a bit long-winded.
You are currently subscribed to sql_language as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-sql_language-$subst('Recip.MemberIDChar')@p2p.wrox.com