resultset
to be loaded into memory, which may have some performance problems, right?
--min
-Original Message-
From: Jonathan Asbell [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 06, 2001 11:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Suggestion/Idea for iterate tag: Iterate ResultSets
Result
PROTECTED]
Subject: Re: Suggestion/Idea for iterate tag: Iterate ResultSets
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
-Original Message-
From: Mindaugas Idzelis [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 9:06 AM
To: [EMAIL PROTECTED]; Jonathan Asbell
Subject: RE: Suggestion/Idea for iterate tag: Iterate ResultSets
I just thought of another option: If resultsets are tied to a connection
is greatly appreciated. I think this would be a great
addition to the taglibs framework.
--min
-Original Message-
From: Jonathan Asbell [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 06, 2001 11:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Suggestion/Idea for iterate tag: Iterate
To: [EMAIL PROTECTED]; Jonathan Asbell
Subject: RE: Suggestion/Idea for iterate tag: Iterate ResultSets
I just thought of another option: If resultsets are tied to a
connection and
a statement, then specify the sql query within the iterator:
Hypothetical taglibs:
sql:query id=myQuery
See this for remote resultsets...
http://developer.java.sun.com/developer/earlyAccess/crs/
also there is a good section in Professional Java Server Programming J2EE
Edition (Wrox press) Page 587 on a TableModel tag library...
Lewis
-Original Message-
From: Mindaugas Idzelis
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
7 matches
Mail list logo
