Re: time type strange behaviour

From: garry saddington <garry(at)schoolteachers(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: time type strange behaviour
Date: 2006-10-10 16:16:14
Message-ID: 1160496974.13498.17.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 2006-10-10 at 11:58 -0400, Tom Lane wrote:
> garry saddington <garry(at)schoolteachers(dot)co(dot)uk> writes:
> > I have the following table def.
> > CREATE TABLE periods
> > (
> > periodid serial NOT NULL,
> > periodnumber integer NOT NULL,
> > periodstart time with time zone,
> > periodend time with time zone,
> > PRIMARY KEY (periodid)
> > )
>
> > This definition does not insert time zone. If I use without time zone
> > then the time zone is inserted.
> > If I input a time like: 01:05 AM then on select I get something like:
> > 1970/01/01 01:05:00:00.
>
> Better look again --- if you get that output, the column is most
> certainly not a time column --- it must be timestamp. Perhaps you
> got confused about which table is which?
>
> regards, tom lane
No, there is no confusion, I have dropped it, re-made it and tested it
again, same result. I know it sounds odd but this is what happens!
Garry

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Page 2006-10-10 16:23:24 Re: [PERFORM] Postgre 8.0 Installation - Issues
Previous Message Joshua D. Drake 2006-10-10 16:11:26 Re: [PERFORM] Postgre 8.0 Installation - Issues