Yes, JdbcTemplate is not a substitute for transaction management. You still benefit from database transactions, so userService.updateUser will operate in a database transaction, but if accountService.updateXXX fails, userService.updateUser will not rollback. If you don’t want to use AOP, you can use TransactionTemplate instead. See programmatic transaction management in the Spring Reference Documentation. One pattern I’ve … Read more
It would help a lot to know what your SQL query looks like, but assuming it’s something like SELECT STREET_NAME FROM table WHERE ID=1; CODE: public String getStreetNameById(int id) { JdbcTemplate jdbcTemplate = new JdbcTemplate(dataSource); String sql = “SELECT STREET_NAME FROM table WHERE ID=?”; String streetName = (String) jdbcTemplate.queryForObject( sql, new Object[] { id }, … Read more
It most certainly does. This example is straight from the Spring 3.0 docs (but is the same in 2.*): String lastName = this.jdbcTemplate.queryForObject( “select last_name from t_actor where id = ?”, String.class, 1212L); As you can see, it strongly favors prepared statements (which it must be using behind the scenes for you): you specify the … Read more
These parameters in the JDBC connection URL can make a big difference in the speed of batched statements — in my experience, they speed things up: ?useServerPrepStmts=false&rewriteBatchedStatements=true See: JDBC batch insert performance
It should looks like this: @Bean(name = “jdbcSlave”) @Autowired public JdbcTemplate slaveJdbcTemplate(@Qualifier(“dsSlave”) DataSource dsSlave) { return new JdbcTemplate(dsSlave); }
Definitely the first way is the best practice, because in the second way you are hitting the database twice where you should actually hit it only once. This can cause performance issues. What you need to do is catch the exception EmptyResultDataAccessException and then return null back. Spring JDBC templates throws back an EmptyResultDataAccessException exception … Read more
You can do what you want. The javadoc of JdbcTemplate even clearly says it: Can be used within a service implementation via direct instantiation with a DataSource reference, or get prepared in an application context and given to services as bean reference.
By default, the JDBCTemplate does its own PreparedStatement internally, if you just use the .update(String sql, Object … args) form. Spring, and your database, will manage the compiled query for you, so you don’t have to worry about opening, closing, resource protection, etc. One of the saving graces of Spring. A link to Spring 2.5’s … Read more
you need to write this structure on your bean configuration (this is your datasource): <bean id=”hikariConfig” class=”com.zaxxer.hikari.HikariConfig”> <property name=”poolName” value=”springHikariCP” /> <property name=”connectionTestQuery” value=”SELECT 1″ /> <property name=”dataSourceClassName” value=”${hibernate.dataSourceClassName}” /> <property name=”maximumPoolSize” value=”${hibernate.hikari.maximumPoolSize}” /> <property name=”idleTimeout” value=”${hibernate.hikari.idleTimeout}” /> <property name=”dataSourceProperties”> <props> <prop key=”url”>${dataSource.url}</prop> <prop key=”user”>${dataSource.username}</prop> <prop key=”password”>${dataSource.password}</prop> </props> </property> </bean> <!– HikariCP configuration –> <bean … Read more
If you do all you can to make both implementations very fast, the JDBC template will probably be a bit faster, because it doesn’t have the overhead that Hibernate has. But it will probably take much more time and lines of code to implement. Hibernate has its learning curve, and you have to understand what … Read more