Re: Syntax for converting double to a timestamp - Mailing list pgsql-general

From Frank Church
Subject Re: Syntax for converting double to a timestamp
Date
Msg-id 84b7c6460609051430t469419e3h64dc8b25d5b03e0d@mail.gmail.com
Whole thread Raw
In response to Re: Syntax for converting double to a timestamp  ("codeWarrior" <gpatnude@hotmail.com>)
Responses Re: Syntax for converting double to a timestamp  (Ron Johnson <ron.l.johnson@cox.net>)
List pgsql-general
On 9/5/06, codeWarrior <gpatnude@hotmail.com> wrote:
> It's generally considered bad form to use reserved words as column names....
>

I am aware of that - in this case  the column names are chosen to
reflect exactly the names of the attributes of the event being
recorded.



>
>
>
> ""Frank Church"" <voipfc@googlemail.com> wrote in message
> news:84b7c6460609031557w1d5aab2t235ff2bdea2124ea@mail.gmail.com...
> >I am trying to create a view based on this query
> >
> > 'select *, "timestamp"::timestamp from ccmanager_log'
> >
> >
> > This is the error I get to below, how do I use the time zone syntax
> >
> > error: cannot cast tupe double precision to timestamp without time zone
> >
> > What is the right syntax?
> >
> >
> > The column to be converted is also called timestamp
> >
> > F Church
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> >       choose an index scan if your joining column's datatypes do not
> >       match
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: what fired a trigger
Next
From: Ron Johnson
Date:
Subject: Re: Syntax for converting double to a timestamp