Re: Proposal - temporal contrib module - Mailing list pgsql-hackers

From tomas@tuxteam.de
Subject Re: Proposal - temporal contrib module
Date
Msg-id 20091105083310.GA11172@tomas
Whole thread Raw
In response to Re: Proposal - temporal contrib module  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Nov 04, 2009 at 09:47:03AM -0800, Jeff Davis wrote:
> On Wed, 2009-11-04 at 12:08 -0500, Chris Browne wrote:
> > I'm
> > a lot less certain about the merits of PK/FK constraints - it is a lot
> > less obvious what forms of constraints will be able to be applied to
> > particular applications.
> 
> Can you clarify, a little?
> 
> A temporal key just means "non-overlapping periods of time", and that
> has a very clear meaning with respect to scheduling.

That would be the main application, I imagine. But "contained in" (and
its reverse) seem good candidates as well. As might be "befoe" and
"after", strictly or not.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFK8o3GBcgs9XrR2kYRAjWOAJ4lrIjJxf1UAN4tyXaVhGtlLGt8SgCeKJje
AvC6Kce87NU3nyOz82ccXaQ=
=Lrk8
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Shall we just get rid of plpgsql's RENAME?
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: Shall we just get rid of plpgsql's RENAME?