>I would suggest using stored procedures to get exactly the number of row
>you want. Transferring more data than you need in a query takes time as
>mentioned in earlier replies from everyone. Other issues are related to
>connection pooling and scalability. If you're query returns several
>hundred
I would suggest using stored procedures to get exactly the number of row
you want. Transferring more data than you need in a query takes time as
mentioned in earlier replies from everyone. Other issues are related to
connection pooling and scalability. If you're query returns several
hundred or t
Just to amplify what Hans said, the reason that retrieving a row count
isn't problematic in JSTL is that the exposed interface ("Result") is
designed to cache rows. Effectively, JSTL does "count the rows as you
fetch them," and ${result.rowCount} simply resolves to the internal
counter we keep.
Paul DuBois wrote:
> At 14:57 -0700 5/6/02, Hans Bergsten wrote:
>
>> Paul DuBois wrote:
>>
>>> After issuing a SELECT query with , you can access the row
>>> count with ${rs.rowCount} (where rs is the result set variable).
>>>
>>> However, in other APIs such as Perl DBI, the equivalent construct
At 14:57 -0700 5/6/02, Hans Bergsten wrote:
>Paul DuBois wrote:
>>After issuing a SELECT query with , you can access the row
>>count with ${rs.rowCount} (where rs is the result set variable).
>>
>>However, in other APIs such as Perl DBI, the equivalent construct
>>is deprecated because some driver
Paul DuBois wrote:
> After issuing a SELECT query with , you can access the row
> count with ${rs.rowCount} (where rs is the result set variable).
>
> However, in other APIs such as Perl DBI, the equivalent construct
> is deprecated because some drivers do not return a count reliably;
> the recom
After issuing a SELECT query with , you can access the row
count with ${rs.rowCount} (where rs is the result set variable).
However, in other APIs such as Perl DBI, the equivalent construct
is deprecated because some drivers do not return a count reliably;
the recommended course of action is to c
