Java PreparedStatement.toString方法代碼示例

import java.sql.PreparedStatement; //導入方法依賴的package包/類
@Override
public PreparedStatement createPreparedStatement(Connection con) throws SQLException {
    PreparedStatement ps = con.prepareStatement(this.sql, autoGeneratedKey);

    if (null != args){
        SQLTools.fillStatement(ps, args);
        if (isBatch  && (rowCont = args.length) > 0){
            int success = ps.executeBatch().length ;
            if (success > 0 && success < rowCont){
                logger.warn("The number of successful {}, now successful {} ", rowCont, success );
            }
            rowCont = success;
        }else {
            rowCont = ps.executeUpdate();
        }
        if (rowCont < 1) {
            throw new SQLException("sql:{} On failure.", ps.toString());
        }
    }

    return ps;
}
 

import java.sql.PreparedStatement; //導入方法依賴的package包/類
public void testBug42267() throws Exception {
    MysqlDataSource ds = new MysqlDataSource();
    ds.setUrl(dbUrl);
    Connection c = ds.getConnection();
    String query = "select 1,2,345";
    PreparedStatement ps = c.prepareStatement(query);
    String psString = ps.toString();
    assertTrue("String representation of wrapped ps should contain query string", psString.endsWith(": " + query));
    ps.close();
    ps.toString();
    c.close();
}
 

import java.sql.PreparedStatement; //導入方法依賴的package包/類
/**
 * Gets called by {@code JdbcTemplate.execute} with an active JDBC
 * PreparedStatement. Does not need to care about closing the Statement
 * or the Connection, or about handling transactions: this will all be
 * handled by Spring's JdbcTemplate.
 * <p><b>NOTE:</b> Any ResultSets opened should be closed in finally blocks
 * within the callback implementation. Spring will close the Statement
 * object after the callback returned, but this does not necessarily imply
 * that the ResultSet resources will be closed: the Statement objects might
 * get pooled by the connection pool, with {@code close} calls only
 * returning the object to the pool but not physically closing the resources.
 * <p>If called without a thread-bound JDBC transaction (initiated by
 * DataSourceTransactionManager), the code will simply get executed on the
 * JDBC connection with its transactional semantics. If JdbcTemplate is
 * configured to use a JTA-aware DataSource, the JDBC connection and thus
 * the callback code will be transactional if a JTA transaction is active.
 * <p>Allows for returning a result object created within the callback, i.e.
 * a domain object or a collection of domain objects. Note that there's
 * special support for single step actions: see JdbcTemplate.queryForObject etc.
 * A thrown RuntimeException is treated as application exception, it gets
 * propagated to the caller of the template.
 *
 * @param ps active JDBC PreparedStatement
 *
 * @return a result object, or {@code null} if none
 * @throws SQLException        if thrown by a JDBC method, to be auto-converted
 *                             to a DataAccessException by a SQLExceptionTranslator
 * @throws DataAccessException in case of custom exceptions
 * @see JdbcTemplate#queryForObject(String, Object[], Class)
 * @see JdbcTemplate#queryForList(String, Object[])
 */
@Override
public T doInPreparedStatement(PreparedStatement ps) throws SQLException, DataAccessException {

    SQLTools.fillStatement(ps, args);
    if (isBatch   && (rowCont = args.length) > 0){
        int success = ps.executeBatch().length ;
        if (success > 0 && success < rowCont){
            logger.warn("The number of successful {}, now successful {} ", rowCont, success );
        }
        rowCont = success;
    }else {
        rowCont = ps.executeUpdate();
    }

    if (rowCont < 1) {
        throw new SQLException("sql:{} On failure.", ps.toString());
    }

    if (this.isInsert){
        if (entityPersister.getIdField().autoGeneratedKeys()){
            id = generated(ps);
        }
        return id;
    }

    return (T) (Object)rowCont;


}