pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Gelbard <gelbardn@intus.net>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] searching time arrays
Date: Thu, 19 Aug 1999 15:17:45 -0400
Message-ID: <8235.935090265@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.3.96.990819113459.5869A-100000@floyd>

Nathan Gelbard <gelbardn@intus.net> writes:
> given the table below, how would i determine which name is
> avail on a givin day at a givin time? the time arrays
> contain an a list of hours a support person is available;
> '{09:00:00,10:00:00,11:00:00,12:00:00}' etc.
> any thoughts?

> CREATE TABLE support_sched
> (
> 		name varchar(30),
> 		monday time[],
> 		tuesday time[],
> 		wednesday time[],
> 		thursday time[],
> 		friday time[],
> 		saturday time[],
> 		sunday time[]
> );

I wouldn't design the table that way --- you've made it really hard
to answer that sort of query, rather than exploiting SQL's strengths.
Instead, consider a table that has one record per availability-window,
say

	name text,
	dayofweek int2,		-- 1-7 = Sun-Sat, or some such encoding
	starttime time,
	stoptime time

and you just make as many of these as there are contiguous time-
windows in each support person's schedule.  There might be twenty
or so records per support person, but so what.  Now your query
looks like

	SELECT name FROM support_sched
	WHERE dayofweek = appropriatevalue AND
		now >= starttime AND now <= stoptime;

(you could also reduce the last two clauses to a BETWEEN if you
happen to like syntactic sugar).

If you're concerned about storing twenty or so copies of a person's
name, make that column be an integer ID code instead that you can look
up in a separate table of support people.  I dunno if I'd bother with
that if the data is *only* a person's name, but as soon as you start
adding phone number, home address, mother's maiden name, yadda yadda
you will want the separate table...

			regards, tom lane



view thread (2+ messages)

Message-ID: <8235.935090265@sss.pgh.pa.us>
Permalink:  ../8235.935090265@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8235.935090265@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, gelbardn@intus.net
  Subject: Re: [SQL] searching time arrays
  In-Reply-To: <8235.935090265@sss.pgh.pa.us>
  References: <Pine.GSO.3.96.990819113459.5869A-100000@floyd> <8235.935090265@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox