Links

Lists

Latest Updates

Ruby On Rails List
Python list
Advanced Java
The JavaScript List
Apache Users
Full Disclosure
Linux Security

Search the archives!
Having a development problem? Ask eDevelopment.org forums!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Too large results

  • From: parikshitp@xxxxxxxx (parikshit)
  • Subject: Too large results
  • Date: Mon, 28 Feb 2000 16:32:52 +0530
This is a multi-part message in MIME format.

------=_NextPart_000_0007_01BF8209.754D9B00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear All,
We have a query which generates a lot of results.
Basically the query is implemented in an ejbFinByXXX() method of an =
Entity Bean.

Now I want to limit the the query result to 10 each time. This I could =
do by setting the fetch size.
ResultSet.setFetchSize(int rows)
and then each time starting from the next location.
ResultSet.absolute(int location)

But I was thinking of some alternative solution. Is there any =
possibility of the following solution being implemented :
When I invoke a finder method the query is being executed and the =
Application Server is receiving query results from database. As this is =
being done I get the first few records in the form of Entity Bean =
instances, while the Application server continues to collect the query =
results in itz cache. This will make the finder nonblocking, as opposed =
to the normal case where the finder method has to wait for all the =
results to be available and creating Primary Key Objects.
This will make the implementation easy, if the Application Server tracks =
the number of records fetched. Maybe I set a property in the Deployment =
Descriptor for the number of beans to create.

I m using WebLogic Server 4.5.1.

Regards,
Parikshit


------=_NextPart_000_0007_01BF8209.754D9B00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear All,<BR>We have a query which =
generates a lot=20
of results.<BR>Basically the query is implemented in an ejbFinByXXX() =
method of=20
an Entity Bean.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now I want to limit the the query =
result to 10 each=20
time. This I could do by setting the fetch =
size.<BR>ResultSet.setFetchSize(int=20
rows)<BR>and then each time starting from the next=20
location.<BR>ResultSet.absolute(int location)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>But I was thinking of some alternative =
solution. Is=20
there any possibility of the following solution being implemented =
:<BR>When I=20
invoke a finder method the query is being executed and the Application =
Server is=20
receiving query results from database. As this is being done I get the =
first few=20
records in the form of Entity Bean instances, while the Application =
server=20
continues to collect the query results in itz cache. This will make the =
finder=20
nonblocking, as opposed to the normal case where the finder method has =
to wait=20
for all the results to be available and creating Primary Key =
Objects.<BR>This=20
will make the implementation easy, if the Application Server tracks the =
number=20
of records fetched. Maybe I set a property in the Deployment Descriptor =
for the=20
number of beans to create.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I m using WebLogic Server =
4.5.1.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>Regards,<BR>Parikshit<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0007_01BF8209.754D9B00--


---
To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx