Recordset Total

Question

Has anyone ever had a problem with recordset totals?
I have a page that is fairly recordset heavy. If the
recordset has more
than 1 record then a select list is displayed, if not, then
just the
value of the single row is displayed.
This is with CS3 by the way.
Whenever I drag a new recordset total to the page to be used
in a
conditional the code that creates the recordset stats gets
overwritten
with the code for current recordset. This prevents my first
conditional
select from displaying.
I have tried recreating the new stats code but that hasn't
made any
difference for some reason. I think I must be missing
something
somewhere. Could it be because the page doesn't actually
display the
total, so when I create a new one Dreamweaver doesn't think
its needed
as it can't see it?
Anyone have any clever ideas?
Steve

Answer 1

If your JDBC driver allows it, and assuming your ResultSet is an instance variable:
private int getResultsCount() throws SQLException {
    _rs.last();
    int numResults = _rs.getRow();
    _rs.beforeFirst();
     return numResults;
}If your JDBC driver doesn't allow you to jump around in the result set like this, you can also populate a Vector with Objects that represent each record in your ResultSet, and then get the size() of that Vector. This has the advantages of allowing you to immediately close the ResultSet object once its data has been stored off into the Vector, since keeping ResultSet objects open while you use them can get messy in certain circumstances:
private Vector getResultsVector(ResultSet rs) {
    Vector resultsVector = new Vector();
    while(rs.next()) {
        String val1 = rs.getString(1);
        String val2 = rs.getString(2);
        String val3 = rs.getString(3);
        Foo myFoo = new Foo(val1, val2, val3);
        resultsVector.addElement(myFoo);
    return resultsVector;
}And lastly, you can always fire off a select count(*) query first which will just return a ResulSet with one row, namely the number of results the query will return. We used to do this, but we found it was more efficient to just issue the query and populate the Vector as described above. Good luck, and ALWAYS remember to close your ResultSets, PreparedStatements, and Connections!