Re: BUG #15145: date time default value issues

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "dibxyooj96(at)gmail(dot)com" <dibxyooj96(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15145: date time default value issues
Date: 2018-04-07 09:35:08
Message-ID: CAKFQuwYRO=7vSY-UbPg0xJ5G_P3s7C7sDTBmC53b1FiXZ6+kaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Friday, April 6, 2018, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Friday, April 6, 2018, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 15145
>> Logged by: Paj Dib Xyooj
>> Email address: dibxyooj96(at)gmail(dot)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. You need to use
"current_timestamp" literal special value if you want insertion time
defaults. But since you didn't create the table in BC with an odd time
zone offset either you gave bad example or there is still something wrong
in your environment.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marko Tiikkaja 2018-04-07 10:08:25 Re: BUG #15145: date time default value issues
Previous Message Takahiro Senda 2018-04-07 09:14:22 installer for windows by enterprisedb doesn't accpet some chars as password