From: | "Frank Church" <voipfc(at)googlemail(dot)com> |
---|---|
To: | codeWarrior <gpatnude(at)hotmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Syntax for converting double to a timestamp |
Date: | 2006-09-05 21:30:21 |
Message-ID: | 84b7c6460609051430t469419e3h64dc8b25d5b03e0d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/5/06, codeWarrior <gpatnude(at)hotmail(dot)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(at)googlemail(dot)com> wrote in message
> news:84b7c6460609031557w1d5aab2t235ff2bdea2124ea(at)mail(dot)gmail(dot)com(dot)(dot)(dot)
> >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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2006-09-05 21:55:42 | Re: Syntax for converting double to a timestamp |
Previous Message | Ivan Sergio Borgonovo | 2006-09-05 20:53:14 | what fired a trigger |