OK, added to TODO.
---
Michael Glaesemann wrote:
On Feb 25, 2006, at 12:09 , Bruce Momjian wrote:
We have this TODO:
o Allow infinite dates just like infinite timestamps
Do we need to add intervals to
On Fri, Feb 24, 2006 at 10:09:25PM -0500, Bruce Momjian wrote:
Karsten Hilbert wrote:
I will also stay with the hope that one day before long we
will have 'infinite'::interval.
We have this TODO:
o Allow infinite dates just like infinite timestamps
Do we need to add
Karsten Hilbert wrote:
Thanks to all for the suggestions.
For the time being I will stay with using NULL.
I will also stay with the hope that one day before long we
will have 'infinite'::interval.
We have this TODO:
o Allow infinite dates just like infinite timestamps
Do we need
On Feb 25, 2006, at 12:09 , Bruce Momjian wrote:
We have this TODO:
o Allow infinite dates just like infinite timestamps
Do we need to add intervals to this?
I think to be consistent with the other datetime types, might as
well. Then one would be able to get an answer to
test=#
Thanks to all for the suggestions.
For the time being I will stay with using NULL.
I will also stay with the hope that one day before long we
will have 'infinite'::interval.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
On Mon, Feb 20, 2006 at 07:24:05PM +0100, Karsten Hilbert wrote:
I am storing the maximum age a vaccination is due in a
patient (eg. don't give this vaccination beyond the age of
10 years or some such). Some vaccinations are to be given
regardless of age.
Up to now I have used NULL to mean
On Tue, Feb 21, 2006 at 12:24:09PM +0900, Michael Glaesemann wrote:
I don't know the details of your database schema,
If you want to you can look it up here:
http://salaam.homeunix.com/twiki/bin/view/Gnumed/DatabaseSchema
Feel free to comment !
but I think the
relationally proper
On Feb 22, 2006, at 1:51 , Karsten Hilbert wrote:
I specifically wanted to avoid that by
something like 'infinite'::interval in some way or other
such that I could always do
... where now date_of_birth + max_age ...
and not need an
... or max_age is null ...
in all the
I am storing the maximum age a vaccination is due in a
patient (eg. don't give this vaccination beyond the age of
10 years or some such). Some vaccinations are to be given
regardless of age.
Up to now I have used NULL to mean no maximum age. That
doesn't really feel right and also complicates the
On Feb 21, 2006, at 3:24 , Karsten Hilbert wrote:
I am storing the maximum age a vaccination is due in a
patient (eg. don't give this vaccination beyond the age of
10 years or some such). Some vaccinations are to be given
regardless of age.
Up to now I have used NULL to mean no maximum age.
10 matches
Mail list logo
