Try turning auto-commit off: // make sure autocommit is off connection.setAutoCommit(false); st = connection.createStatement(); st.setFetchSize(1000); System.out.println(“start query “); rs = st.executeQuery(queryString); System.out.println(“done query”); Reference
Thank you for your feedback. The Microsoft JDBC Driver for SQL Server does not yet support JRE 1.7. We are aware of the getDate issue between our JDBC driver & JRE 1.7 and we are looking into publishing a hotfix to enable customers to move forward with non-production testing of our driver with JRE 1.7. … Read more
I think the best answer has already being mentioned, but I thought it could be interesing to mention that you could consider the new JDK 7 feature of autoclosable resources. try{ try(Connection conn = DriverManager.getConnection(“jdbc:mysql://localhost/hrdb”, “obiwan”, “kenobi”); Statement stm = conn.createStatement(); ResultSet rs = stm.executeQuery(“select name from department”)) { while(rs.next()){ System.out.println(rs.getString(“name”)); } } }catch(SQLException e){ … Read more
As mentioned by james, Statement.cancel() will cancel the execution of a running Statement (select, update, etc). The JDBC docs specifically say that Statement.cancel() is safe to run from another thread and even suggests the usage of calling it in a timeout thread. After canceling the statement, you’re still stuck with the job of rolling back … Read more
See jTDS FAQ http://jtds.sourceforge.net/faq.html you will have to pass useNTLMv2=true and domain=yourdomain
First, the PreparedStatement placeholders (those ? things) are for column values only, not for table names, column names, SQL functions/clauses, etcetera. Better use String#format() instead. Second, you should not quote the placeholders like ‘?’, it would only malform the final query. The PreparedStatement setters already do the quoting (and escaping) job for you. Here’s the … Read more
The “14” and “6” in those driver names refer to the JVM they were written for. If you’re still using JDK 1.4 I’d say you have a serious problem and need to upgrade. JDK 1.4 is long past its useful support life. It didn’t even have generics! JDK 6 u21 is the current production standard … Read more
As said before encrypting passwords is just moving the problem somewhere else. Anyway, it’s quite simple. Just write a class with static fields for your secret key and so on, and static methods to encrypt, decrypt your passwords. Encrypt your password in Tomcat’s configuration file (server.xml or yourapp.xml…) using this class. And to decrypt the … Read more
When you use JdbcTemplate you give it SQL that has a ? placeholder for each parameter you want substituted into the SQL. When you assign parameters in the code you have to pass in arguments in an array and they get used in the order in which they appear in the array, like this: Object[] … Read more
You can’t put anything in the connection URL. In Oracle each user has their own schema (even if doesn’t contain any objects) and that is their default schema. Once logged in/connected, they can change their default schema with an ALTER SESSION SET CURRENT_SCHEMA=animals So you’d need to do the extra statement after connecting. It is … Read more