Re: Problem with timestamp field/time function.. (upgrading - Mailing list pgsql-sql

From Stephan Szabo
Subject Re: Problem with timestamp field/time function.. (upgrading
Date
Msg-id 20020822072508.V6679-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: Problem with timestamp field/time function.. (upgrading  (Lucas Brasilino <brasilino@recife.pe.gov.br>)
List pgsql-sql
On Thu, 22 Aug 2002, Lucas Brasilino wrote:

> Hi Stephan
>
> >>    So, how can I get the same result above without using time() ??
> >>Or if it not possible, how can I extract (yes, I tried with extract()
> >>function too) time from a timestamp column?
> >>    I know it's quite simple question... but I haven't find any clue!
> >>
> >
> > In general you could probably use CAST(materiadata as time) I'd guess.
> > I believe that at this point you can still use the functions, you just
> > need to double quote them ("time"(materiadata)) to differentiate them
> > from the type specifiers.
> >
>
>     Well, it seems to work only with "timestamp without time zone" type. But
> worked. Thanks a lot.
>     For me it's a new approching not using functions such as time, but
> "casting" it to a "time" type ( like <sql>select materiadata::time from
> materia;</sql>).
>     If PostgreSQL development group change it's point of view, I suppose
> there's some advantage. Do you know some advantages ??

time(n) and timestamp(n) refer to a type which I believe gives n digits of
fractional seconds in SQL. Compatibility for that SQL feature was added
but the syntax collided with the old usage.  In any case the old time()
etc were actually typecasts since it was a direct call to the type casting
function.




pgsql-sql by date:

Previous
From: Andrew Klimov
Date:
Subject: bytea etc.
Next
From: Bruce Momjian
Date:
Subject: Re: BITMAP INDEXES...