From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | "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:48:17 |
Message-ID: | CAKFQuwa+9EYiQNTjYkXwGK4Kyu1GjyOCOBuBkuNi8UmkcQjbaA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday, January 4, 2019, Rich Shepard <rshepard(at)appl-ecosys(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2019-01-04 17:53:43 | Re: Comparing dates in DDL |
Previous Message | Rich Shepard | 2019-01-04 17:36:07 | Re: Comparing dates in DDL |