Re: Comparing dates in DDL

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Comparing dates in DDL
Date: 2019-01-04 17:36:07
Message-ID: alpine.LNX.2.20.1901040934000.29312@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 4 Jan 2019, David G. Johnston wrote:

>> I wondered about this since NULL can be missing, unknown, or otherwise
>> defined. Are there benefits to allowing an empty value in that column when
>> checking that it's later than the start date rather than explicitly setting
>> a default date after the start date?
>>
>>
> I don’t understand the question...

David,

Understandable. :-)

Perhaps this is more clear: is there a difference between not specifying a
default end_date value and specifying NULL as the default end_date value?

Regards,

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2019-01-04 17:48:17 Re: Comparing dates in DDL
Previous Message Pavel Stehule 2019-01-04 17:35:19 Re: (Again) Column Store on PostGreSQL