[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/ ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
