From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | John Smith <pbucherjr(at)yahoo(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: upgrade problems |
Date: | 2003-04-23 18:32:00 |
Message-ID: | 20030423113004.O86759-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, 21 Apr 2003, John Smith wrote:
> I'm trying to use 7.22 , coming from 7.1 but I get the
> error on 7.3 as well. My problems is with dates
> though. I get this error when trying to do a query
> that worked on 7.1
>
> The query : SELECT id, occurs,
> to_char(timestamp('now',starttime),'HH12:MI PM') as
> starttime, to_char(timestamp('now',endtime),'HH12:MI
> PM') as endtime, location FROM site_interview_sessions
> WHERE job_id = 730 AND timezone = timezones.id AND
> occurs >= 'now' ORDER BY occurs,
> to_char(timestamp('now',starttime),'HH24:MI'),
> to_char(timestamp('now',endtime),'HH24:MI'), generated
> this error ERROR: parser: parse error at or near
> \"\'\" !
> I tried changing a few things around, but got no good
> results. Is there something with any of these
> functions I've used improperly that may be causeing
> this query to malfunction? Thanks in advance.
My guess is the use of the timestamp function. You'll need to use
"timestamp"('now', ...) to call the function (Rather than it being the
type with an precision specification). However, what are you actually
trying to get from those calls in any case?
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-04-23 18:33:42 | Re: no password required |
Previous Message | Shankar K | 2003-04-23 18:21:58 | DB block size Vs filesystem buffer size |