Horton

Re: BUG #15145: date time default value issues

Marko Tiikkaja <marko@joh.to>

View thread
From: Marko Tiikkaja <marko@joh.to>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: "dibxyooj96@gmail.com" <dibxyooj96@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2018-04-07T10:08:25Z
Lists: pgsql-bugs 
On Sat, Apr 7, 2018 at 12:35 PM, David G. Johnston <
david.g.johnston@gmail.com> wrote:

> On Friday, April 6, 2018, David G. Johnston <david.g.johnston@gmail.com>
> wrote:
>
>> On Friday, April 6, 2018, PG Bug reporting form <noreply@postgresql.org>
>> wrote:
>>
>>> The following bug has been logged on the website:
>>>
>>> Bug reference:      15145
>>> Logged by:          Paj Dib Xyooj
>>> Email address:      dibxyooj96@gmail.com
>>> PostgreSQL version: 9.4.5
>>> Operating system:   (Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit
>>> Description:
>>>
>>> i set column "document_datenow timestamp with time zone NOT NULL DEFAULT
>>> now()"
>>> but the values that like this "0001-12-31 23:42:04+06:42:04 BC"
>>>
>>
>> What does typing "date" at your o/s command line show?
>>
>>
> So, that a constant time is used is not unusual, it's documented.  Now()
> is a function that gets resolved at default creation.
>

That's not correct.  You're thinking of  DEFAULT 'now'.  DEFAULT now()
works just fine.


.m