[Pljava-dev] ResultSetHandle problem

Thomas, it is great to have this bug solved!
I will test it as soon as I have some time.
Filip

----- Original Message -----
From: "Thomas Hallgren" <thomas at tada.se>
To: "lifeng" <lifenggod at 263.net>; "Filip Hrbek" <filip.hrbek at plz.comstar.cz>
Cc: "pljava-dev" <pljava-dev at gborg.postgresql.org>
Sent: Monday, January 23, 2006 12:51 PM
Subject: Re: [Pljava-dev] ResultSetHandle problem

> Hi,
> The bug concerning different return types for methods using SETOF RECORD
> (http://gborg.postgresql.org/project/pljava/bugs/bugupdate.php?1440) is
> resolved and new source is available in CVS HEAD. You're welcome to try
> it out. If you don't have access to CVS you may use a temporary source
> bundle (http://www.tada.se/pub/pljava-src-1.2.dev.tar.gz)
>
> Please let me know how if you have further problems.
>
> Regards,
> Thomas Hallgren
>
> Thomas Hallgren wrote:
>> Lifeng,
>> This is a known bug
>> (http://gborg.postgresql.org/project/pljava/bugs/bugupdate.php?1440)
>> The only way to solve it properly is to fix that bug. I haven't got
>> around to it just yet.
>>
>> Kind regards,
>> Thomas Hallgren
>>
>>
>> lifeng wrote:
>>
>>> I have a function returning set of "record", i.e. there is no
>>> information about the target structure to return until it is actually
>>> called. If I call such a function several times with different target
>>> structures within one session, I got one of two following errors:
>>>
>>> 1)
>>> ERROR: query-specified return row and actual function return row do not
>>> match
>>> 2)
>>> ERROR: java.lang.ArrayIndexOutOfBoundsException: 2
>>>
>>> If I call such a function several times with different target structures
>>> within different sessions, I can got correct result. I guess that pljava
>>> caches the first target structure, though I think that it should be
>>> replaced by a new target structure when I called it with different
>>> target structure. When I test the function with 'sql' language , it is
>>> correct. There should be erro in pljava, not in PostgreSQL.
>>>
>>> How can I solve the problem?
>>>
>>> Regards
>>> lifeng
>>>
>>> ????????lifenggod at 263.net
>>> ??????????2006-01-21
>>> _______________________________________________
>>> Pljava-dev mailing list
>>> Pljava-dev at gborg.postgresql.org
>>> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>>>
>>>
>>
>> _______________________________________________
>> Pljava-dev mailing list
>> Pljava-dev at gborg.postgresql.org
>> http://gborg.postgresql.org/mailman/listinfo/pljava-dev
>>