gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Default datetime precision


From: Busser, Jim
Subject: Re: [Gnumed-devel] Default datetime precision
Date: Sun, 25 Aug 2013 15:39:18 +0000

On 2013-08-25, at 1:28 AM, Karsten Hilbert <address@hidden> wrote:

>> At the creation of an encounter, it is sane that GNUmed offers by default, 
>> and saves, either
>> 
>>      now()
>> 
>> or maybe even better
>> 
>>      date_trunc('minute', now())
> 
> There is no choice in that. All date/time related fields in
> the database are declared "timestamp with time zone" thusly
> storing full precision down to the microsecond. If they
> weren't they COULD NOT store the time which is undesirable.

I would have thought that

        date_trunc('minute', now())

which is

        2013-08-25 08:35:00-08:00

and which contains full precision, down to zero seconds, qualifies as 
"timestamp with time zone".

It is merely that the seconds have been "zeroed out".

-- Jim


reply via email to

[Prev in Thread] Current Thread [Next in Thread]