Result sets ARE tied to the connection in a way. Some DB drivers throw
exceptions when you try to manipulate data while you still have a pointer to
rows. At work we were trying to manipulate a stream which was pointing to
an output parameter in a stored proc while the connection was open. The
result was that we had to convert the stream into another object (String in
our case) and close the connection just to manipulate the data.
----- Original Message -----
From: "Mindaugas Idzelis" <[EMAIL PROTECTED]>
To: "struts" <[EMAIL PROTECTED]>
Sent: Sunday, May 06, 2001 9:33 PM
Subject: Suggestion/Idea for <iterate> tag: Iterate ResultSets
> I just thought up of an excellent idea (although, I wasn't the only one).
> Use the iterate tag to iterate over the rows of a resultset. The column
meta
> data could be exposed as beans named as the column name. A <bean:write>
> operation would display the data in the column.
>
> I did a search about this topic in the mailing list archive, and I found
> this message:
>
> http://marc.theaimsgroup.com/?l=struts-user&m=98269295229785&w=2
>
> It talk about ResultSets being tied to connections. This is not the case.
> ResultSets are tied to the statements that produced them, and as far as I
> can tell, statements are not closed when the connection is closed.
>
> Other than that, It should be easy to change the iterate tag to support
> resultsets. If anyone is interested in helping me extend or develop a tag
> for this purpose, please message me.
>
> --min
>
