PreparedStatement execution cause OutOfMemoryException

Question

Hello,
I use PreparedStatement for getting data from database. It works well unless there is much data to get. If the result set has many rows (over 1000000) I get OutOfMemory error. I tried use Statement instead of PreparedStatement and tried to set my parameters value manually, but it doesn't work (in postgre database):
sqlQuery = select * from employee_tmp where hire_date > ?; PreparedStatement st = connection.prepareStatement(sqlQuery); st.setDate(1, myDate); ResultSet rs = st.executeQuery();
Result is OK, but for much data I get OutOfMemory error.
sqlQuery = select * from employee_tmp where hire_date > myDate.toString(); Statement st = connection.createStatement(); ResultSet rs = st.executeQuery(sqlQuery);
Getting data from database is fast, but I get all records, not only these from the first case.
Thank you for any help in advanced.
Agata

Answer 1

agad wrote:
Hello,
I use PreparedStatement for getting data from database. It works well unless there is much data to get. If the result set has many rows (over 1000000) I get OutOfMemory error. I tried use Statement instead of PreparedStatement and tried to set my parameters value manually, but it doesn't work (in postgre database):
sqlQuery = select * from employee_tmp where hire_date > ?;
PreparedStatement st = connection.prepareStatement(sqlQuery);
st.setDate(1, myDate);
ResultSet rs = st.executeQuery();Result is OK, but for much data I get OutOfMemory error.
sqlQuery = select * from employee_tmp where hire_date > myDate.toString();
Statement st = connection.createStatement();
ResultSet rs = st.executeQuery(sqlQuery);Getting data from database is fast, but I get all records, not only these from the first case.
Thank you for any help in advanced.
AgataThe PreparedStatement itself should definately not cause an OutOfMemoryException. Are you maybe looping through the ResultSet and storing the rows in an List or something? If it is truely the Driver throwing it, then ask at a PostGreSQL Driver forum, and probably post a bug report (to PostGreSQL, not Sun).