From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Michael Horsten <horsten(at)aquavital(dot)de> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1700: Error on Subselect with date in where condition |
Date: | 2005-06-03 16:05:52 |
Message-ID: | 20050603160552.GA35723@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
[Please copy the mailing list on replies. I'm sending this copy of
your message to the list so others can see what the problem was.]
On Fri, Jun 03, 2005 at 05:48:19PM +0200, Michael Horsten wrote:
> I'm really sorry,
> it was my fault.
> I only executed the SQL Statement in "EMS SQL Query", not in the pgAdmin III SQL Query.
> After i pasted the Code in the pgAdminIII it worked fine,
> so:
> It is a problem of the EMS-Tool, not of PostgreSQL!!!!
> Sorry for disturbing you!
>
> On Fri, Jun 03, 2005 at 01:47:46PM +0100, Michael wrote:
> >
> > Description: Error on Subselect with date in where condition
>
> Are you sure that "Subselect with date in where condition" accurately
> describes the conditions that produce the error? Do you get the
> error if you don't use a subselect or if you don't use a date in
> the WHERE condition?
>
> > ERROR: cursor "zeoscursor_91bb_610f34f9ac96" does not exist
>
> One possibility is that you're trying to use a cursor outside of the
> transaction in which it was declared. "zeoscursor_91bb_610f34f9ac96"
> looks automatically generated -- where is it coming from? What
> client interface are you using? How are you handling transactions?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-05 01:52:26 | Re: BUG #1699: Invalid timestamps with timezone and interger timestamps |
Previous Message | Bruno Wolff III | 2005-06-03 14:49:51 | Re: BUG #1697: Select getting slower on continously updating data |