Re: time type strange behaviour

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