0

I have a class that fetches a record but dont think I need to use List object because I am fetching one record and not an array of records.

public List getRecords(){
        ResultSet rs = null;
        Statement stmt = null;
        Connection connection = null;
 
        List rows = new ArrayList();
        
        try
        {
            Class.forName("org.gjt.mm.mysql.Driver");
            connection = DriverManager.getConnection("jdbc:mysql://localhost/dbase?user=myname&password=thepassword");
            stmt = connection.createStatement();
            rs = stmt.executeQuery("SELECT * from user where userid = 10");  
            
            while(rs.next()){
            RowBean row = new RowBean();
            row.setFirstname(rs.getString("firstname"));
            row.setLastname( rs.getString("lastname"));
            rows.add(row); 
            .....

Would this be correct to just return a RowBean object and if so am I doing it correctly?

public RowBean getRecord(){ 
        ResultSet rs = null; 
        Statement stmt = null; 
        Connection connection = null; 
 
 
        //List rows = new ArrayList(); 
        RowBean row = new RowBean();
 
        try 
        { 
            Class.forName("org.gjt.mm.mysql.Driver"); 
            connection = DriverManager.getConnection("jdbc:mysql:// 
localhost/dbase?user=myname&password=thepassword"); 
            stmt = connection.createStatement(); 
            rs = stmt.executeQuery("SELECT * from user where userid = 
10"); 
 
 
            while(rs.next()){ 
           
            row.setFirstname(rs.getString("firstname")); 
            row.setLastname( rs.getString("lastname")); 
            //rows.add(row); 
            }
            ..... 
            //last part of method I would return the RowBean object:
            return row;
}
2
Contributors
1
Reply
2
Views
9 Years
Discussion Span
Last Post by Ezzaral
0

Yes, that would be just fine I would imagine. You don't show the rest of the try block, but be sure to close the statement and connection in a finally{} clause so you don't chew up your database resources.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.