Re: Comparing dates in DDL - Mailing list pgsql-general

From David G. Johnston
Subject Re: Comparing dates in DDL
Date
Msg-id CAKFQuwa+9EYiQNTjYkXwGK4Kyu1GjyOCOBuBkuNi8UmkcQjbaA@mail.gmail.com
Whole thread Raw
In response to Re: Comparing dates in DDL  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Comparing dates in DDL  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
On Friday, January 4, 2019, Rich Shepard <rshepard@appl-ecosys.com> wrote:
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?


No.  If no default is available and a value for the field is not provided the stored value will be null; a default of null is thus also redundant specification.

David J.

pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Comparing dates in DDL
Next
From: Rob Sargent
Date:
Subject: Re: Comparing dates in DDL