Re: HOW-TO do incomplete dates: year, optional month, optional day?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: HOW-TO do incomplete dates: year, optional month, optional day?
Date: 2003-01-23 13:45:27
Message-ID: 20030123134527.GA12942@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jan 22, 2003 at 16:11:09 -0600,
will trillich <will(at)serensoft(dot)com> wrote:
> is there a way, save lots of manual manipulation and
> hand-waving, to implement PARTIAL DATES? (this may be exactly
> the job for creating a new data type, but hopefully someone's
> already invented this wheel...?)
>
> "doug has worked at pinnacle since 1991".
>
> not 1-jan-1991, not 31-dec-1991, but just plain-ol' 1991.

I think if you precisely define what just plain-ol' 1991 means, you
will be able to design a solution that will work.

A couple possible answers are:

Store a lower and upper bound for the dates.

Store a best guess for the date, but only output the most significant
part(s) in reports.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Wolff III 2003-01-23 13:53:18 Re: standard schemas for addresses, others?
Previous Message codeWarrior 2003-01-23 13:20:53 Re: I was spoiled by the MySQL timestamp field