Skip site navigation (1) Skip section navigation (2)

Re: How to setup default value "0000-00-00" for "date"

From: "Jim Wilson" <jimw(at)kelcomaine(dot)com>
To: <hf0722x(at)protecting(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to setup default value "0000-00-00" for "date"
Date: 2004-08-22 22:01:02
Message-ID: twig.1093212062.19696@kelcomaine.com (view raw or flat)
Thread:
Lists: pgsql-general
Harald Fuchs said:

> In article <twig(dot)1093012692(dot)59157(at)kelcomaine(dot)com>,
> "Jim Wilson" <jimw(at)kelcomaine(dot)com> writes:
> 
> > It'd probably be better design to not use the date as a flag.  This issue
> > actually came up for me yesterday with an application that is now being ported
> > to Postgres.  Previously a null "ship date" indicated that an item to be
> > shipped had not gone yet.  I'm adding a flag, not just because of this issue
> > you describe,  but it is also more intuitive for anyone looking at the data
> > who is unfamiliar with the business logic.
> 
> Me thinks that's somewhat unclean.  Is your shipDate nullable?  If
> yes, what's the meaning of "shipDate IS NULL"?  If no, what do you put
> in that field if notYetShipped is true?

Actually it would be a boolean "shipped" flag.  ShipDate can be whatever you
want.  Perhaps even null.  All in all it just makes sense to use the boolean
when you need a flag (or integer or char for more than two flag states).

Best,

Jim


In response to

pgsql-general by date

Next:From: Thomas HallgrenDate: 2004-08-22 22:02:02
Subject: Re: Unsupported 3rd-party solutions (Was: Few questions
Previous:From: Bruce MomjianDate: 2004-08-22 20:43:24
Subject: Re: Unsupported 3rd-party solutions (Was: Few questions on

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group