| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Brent Wood <b(dot)wood(at)niwa(dot)co(dot)nz> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Partial dates |
| Date: | 2005-09-15 01:36:04 |
| Message-ID: | 20050915013604.GB12198@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Sep 14, 2005 at 03:49:29PM +1200, Brent Wood wrote:
> In case anyone is interested, right now we store year, month & day and
> have a timestamp field where the entire field is null if any one part is
> unknown.
>
> Are there any better ways in Postgres?
You can create a new type, which is a privilege you don't have in some
other systems. Or you can separate the column in three columns and
leave some of them NULL as appropiate.
--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended." (Gerry Pourwelle)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Fabiani | 2005-09-15 02:06:19 | Re: Speed problems |
| Previous Message | christomec | 2005-09-14 21:34:00 | importing shape files nightmare! |