View Single Post

   
  #5 (permalink)  
Old 04-16-2008, 01:58 AM
Kris Jurka
 
Posts: n/a
Default Re: ResultSet with more than 5 rows causes error



On Mon, 1 Oct 2007, Kris Jurka wrote:

> I've managed to reproduce this problem with the attached test case.
> At fault are the ill conceived side effects in
> org.postgresql.core.v3.SimpleParameterList#getType OID. An accessor
> like getTypeOID shouldn't be responsible for setting a value for the
> out parameter. getTypeOID is called from QueryExecutorImpl's
> sendParse method, which obviously isn't called when we reuse a server
> side prepared statement and don't need to reparse. This leaves an
> uninitialized value in the paramValues array which we die on later.
>


I've applied a fix for this in CVS to 8.1, 8.2 and 8.3dev and it will be
included in the next release.

Kris Jurka

---------------------------(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

Reply With Quote