From: | tomas(at)tuxteam(dot)de |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal - temporal contrib module |
Date: | 2009-11-05 08:33:10 |
Message-ID: | 20091105083310.GA11172@tomas |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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-----
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2009-11-05 10:18:22 | Re: Shall we just get rid of plpgsql's RENAME? |
Previous Message | Craig Ringer | 2009-11-05 06:17:17 | Re: Shall we just get rid of plpgsql's RENAME? |