struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen, Dean (Zhun)" <Dean.C...@gs.com>
Subject RE: Large resultsets & best practices
Date Wed, 08 May 2002 18:16:27 GMT
Are there good tutorials on resultsets, JDBC, cursors, etc. other than just
the API? 

Dean Chen


-----Original Message-----
From: Robert [mailto:rmcintosh@bull-enterprises.com]
Sent: Wednesday, May 08, 2002 2:10 PM
To: 'Struts Users Mailing List'
Subject: RE: Large resultsets & best practices


The javadocs tell you exactly. Go to:
http://java.sun.com/j2se/1.3/docs/api/index.html

And then to java.sql.ResultSet. Those constants are described there.

- Robert

-----Original Message-----
From: Chen, Dean (Zhun) [mailto:Dean.Chen@gs.com] 
Sent: Wednesday, May 08, 2002 1:07 PM
To: 'Struts Users Mailing List'
Subject: RE: Large resultsets & best practices

Yes, we will be using a connection pool also. However, in my past
projects,
I've seen developers use statments of type
(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY) with
WebLogic connection pools. What kind of cursor is that?

Thanks,

Dean Chen


-----Original Message-----
From: Steven Banks [mailto:SDBANKS@vac-acc.gc.ca]
Sent: Wednesday, May 08, 2002 12:48 PM
To: struts-user@jakarta.apache.org
Subject: Re: Large resultsets & best practices


I am going to be looking at this shortly also.  My only other
consideration
is that we use a connection pool and so the cursor will not be open
while we
are scrolling.  Is this also a requirement for you framework?



Steven Banks
368-0566

>>> "Chen, Dean (Zhun)" <Dean.Chen@gs.com> 05/08/02 01:33PM >>>
Hi,
I have a design question. We are trying to build a struts based web
framework for our department. However, we are running into a few
performance
related questions when it comes to large resultsets from the database. 

1. After one makes a call to the database, what is the best way (best
practice?) to store the results and to iterate through them?
      Should one create an object and store all results into the object?
I
believe that would cause out of memory errors of the JVM.
      What kind of cursor would one use? Are there any good tutorials on
different types of cursors and usages?

2. We want to make our framework as flexible as possible (doesn't
everyone
else?). What would be a good design so we can display contents on web
pages,
(including pagination), and have a full dump to a CSV file directly. 

I would welcome any ideas or explanations of your current
implementations.
We are not using EJBs, so I don't know if the Java BluePrint with DAO
would
apply very well?

Thanks,

Dean Chen

--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>



--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>

--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>



--
To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message