问题是关于RowMapper在主/详细场景中的最佳实践用法,我们希望使用spring jdbc急切地获取详细信息。
假设我们同时拥有Invoice和InvoiceLine类。
public class Invoice{
private BigDecimal invId;
private Date invDate;
private List<InvoiceLine> lines;
}
public class InvoiceLine{
private int order;
private BigDecimal price;
private BigDecimal quantity;
}
将Spring Jdbc与行映射器一起使用时,我们通常会有一个
public class InvoiceMapper implements RowMapper<Invoice>{
public Invoice mapRow(ResultSet rs, int rowNum) throws SQLException {
Invoice invoice = new Invoice();
invoice.setInvId(rs.getBigDecimal("INVID"));
invoice.setInvDate(rs.getDate("INVDATE"));
return invoice;
}
}
现在问题是我想急切地获取与此发票实例相关的InvoiceLine。 如果我在rowmapper类中查询数据库会没关系吗?或者任何人更喜欢另一种方式?我使用下面的模式,但不满意。
public class InvoiceMapper implements RowMapper<Invoice>{
private JdbcTemplate jdbcTemplate;
private static final String SQLINVLINE=
"SELECT * FROM INVOICELINES WHERE INVID = ?";
public Invoice mapRow(ResultSet rs, int rowNum) throws SQLException {
Invoice invoice = new Invoice();
invoice.setInvId(rs.getBigDecimal("INVID"));
invoice.setInvDate(rs.getDate("INVDATE"));
invoice.setLines(jdbcTemplate.query(SQLINVLINE,
new Object[]{invoice.getInvId},new InvLineMapper());
return invoice;
}
}
我觉得这种方法有问题,但无法获得更好的方法。如果有人能告诉我为什么这是一个糟糕的设计,我会非常高兴,如果有的话,那将是正确的用法。
答案 0 :(得分:18)
ResultSetExtractor是更好的选择。执行一个连接两个表的查询,然后迭代结果集。您需要有一些逻辑来聚合属于同一发票的多个行 - 通过按发票ID排序并检查ID何时更改或使用如下例中所示的映射。
jdbcTemplate.query("SELECT * FROM INVOICE inv JOIN INVOICE_LINE line " +
+ " on inv.id = line.invoice_id", new ResultSetExtractor<List<Invoice>>() {
public List<Invoice> extractData(ResultSet rs) {
Map<Integer,Invoice> invoices = new HashMap<Integer,Invoice>();
while(rs.hasNext()) {
rs.next();
Integer invoiceId = rs.getInt("inv.id");
Invoice invoice = invoces.get(invoiceId);
if (invoice == null) {
invoice = invoiceRowMapper.mapRow(rs);
invoices.put(invoiceId,invoice);
}
InvoiceItem item = invLineMapper.mapRow(rs);
invoice.addItem(item);
}
return invoices.values();
}
});
答案 1 :(得分:4)
您在此处重新创建了1 + n
问题。
要解决此问题,您需要将外部查询更改为连接,然后手工制作循环以将平面连接结果集解析为Invoice 1 -> * InvLine
List<Invoice> results = new ArrayList<>();
jdbcTemplate.query("SELECT * FROM INVOICE inv JOIN INVOICE_LINE line on inv.id = line.invoice_id", null,
new RowCallbackHandler() {
private Invoice current = null;
private InvoiceMapper invoiceMapper ;
private InvLineMapper lineMapper ;
public void processRow(ResultSet rs) {
if ( current == null || rs.getInt("inv.id") != current.getId() ){
current = invoiceMapper.mapRow(rs, 0); // assumes rownum not important
results.add(current);
}
current.addInvoiceLine( lineMapper.mapRow(rs, 0) );
}
}
我显然没有编译过这个...希望你能得到这个想法。还有另一种选择,使用hibernate或任何JPA实现,他们开箱即用,可以节省大量时间。
更正:应该真正使用@gkamal在他的回答中使用的ResultSetExtractor
,但是所有逻辑仍然存在。
答案 2 :(得分:1)
基于ResultSetExtractor
的公认解决方案可以更加模块化和可重用:在我的应用程序中,我创建了一个CollectingRowMapper
接口和一个抽象实现。请参阅下面的代码,它包含Javadoc注释。
import org.springframework.jdbc.core.RowMapper;
/**
* A RowMapper that collects data from more than one row to generate one result object.
* This means that, unlike normal RowMapper, a CollectingRowMapper will call
* <code>next()</code> on the given ResultSet until it finds a row that is not related
* to previous ones. Rows <b>must be sorted</b> so that related rows are adjacent.
* Tipically the T object will contain some single-value property (an id common
* to all collected rows) and a Collection property.
* <p/>
* NOTE. Implementations will be stateful (to save the result of the last call
* to <code>ResultSet.next()</code>), so <b>they cannot have singleton scope</b>.
*
* @see AbstractCollectingRowMapper
*
* @author Pino Navato
**/
public interface CollectingRowMapper<T> extends RowMapper<T> {
/**
* Returns the same result of the last call to <code>ResultSet.next()</code> made by <code>RowMapper.mapRow(ResultSet, int)</code>.
* If <code>next()</code> has not been called yet, the result is meaningless.
**/
public boolean hasNext();
}
import java.sql.ResultSet;
import java.sql.SQLException;
/**
* Basic implementation of {@link CollectingRowMapper}.
*
* @author Pino Navato
**/
public abstract class AbstractCollectingRowMapper<T> implements CollectingRowMapper<T> {
private boolean lastNextResult;
@Override
public T mapRow(ResultSet rs, int rowNum) throws SQLException {
T result = mapRow(rs, null, rowNum);
while (nextRow(rs) && isRelated(rs, result)) {
result = mapRow(rs, result, ++rowNum);
}
return result;
}
/**
* Collects the current row into the given partial result.
* On the first call partialResult will be null, so this method must create
* an instance of T and map the row on it, on subsequent calls this method updates
* the previous partial result with data from the new row.
*
* @return The newly created (on the first call) or modified (on subsequent calls) partialResult.
**/
protected abstract T mapRow(ResultSet rs, T partialResult, int rowNum) throws SQLException;
/**
* Analyzes the current row to decide if it is related to previous ones.
* Tipically it will compare some id on the current row with the one stored in the partialResult.
**/
protected abstract boolean isRelated(ResultSet rs, T partialResult) throws SQLException;
@Override
public boolean hasNext() {
return lastNextResult;
}
protected boolean nextRow(ResultSet rs) throws SQLException {
lastNextResult = rs.next();
return lastNextResult;
}
}
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.ArrayList;
import java.util.List;
import org.springframework.jdbc.core.ResultSetExtractor;
import org.springframework.util.Assert;
/**
* A ResultSetExtractor that uses a CollectingRowMapper.
* This class has been derived from the source code of Spring's RowMapperResultSetExtractor.
*
* @author Pino Navato
**/
public class CollectingRowMapperResultSetExtractor<T> implements ResultSetExtractor<List<T>> {
private final CollectingRowMapper<T> rowMapper;
private final int rowsExpected;
/**
* Create a new CollectingRowMapperResultSetExtractor.
* @param rowMapper the RowMapper which creates an object for each row
**/
public CollectingRowMapperResultSetExtractor(CollectingRowMapper<T> rowMapper) {
this(rowMapper, 0);
}
/**
* Create a new CollectingRowMapperResultSetExtractor.
* @param rowMapper the RowMapper which creates an object for each row
* @param rowsExpected the number of expected rows (just used for optimized collection handling)
**/
public CollectingRowMapperResultSetExtractor(CollectingRowMapper<T> rowMapper, int rowsExpected) {
Assert.notNull(rowMapper, "RowMapper is required");
this.rowMapper = rowMapper;
this.rowsExpected = rowsExpected;
}
@Override
public List<T> extractData(ResultSet rs) throws SQLException {
List<T> results = (rowsExpected > 0 ? new ArrayList<>(rowsExpected) : new ArrayList<>());
int rowNum = 0;
if (rs.next()) {
do {
results.add(rowMapper.mapRow(rs, rowNum++));
} while (rowMapper.hasNext());
}
return results;
}
}
上面的所有代码都可以作为库重用。您只需子类AbstractCollectingRowMapper
并实现两个抽象方法。
给出如下查询:
SELECT * FROM INVOICE inv
JOIN INVOICELINES lines
on inv.INVID = lines.INVOICE_ID
order by inv.INVID
您只能为两个连接表编写一个映射器:
public class InvoiceRowMapper extends AbstractCollectingRowMapper<Invoice> {
@Override
protected Invoice mapRow(ResultSet rs, Invoice partialResult, int rowNum) throws SQLException {
if (partialResult == null) {
partialResult = new Invoice();
partialResult.setInvId(rs.getBigDecimal("INVID"));
partialResult.setInvDate(rs.getDate("INVDATE"));
partialResult.setLines(new ArrayList<>());
}
InvoiceLine line = new InvoiceLine();
line.setOrder(rs.getInt("ORDER"));
line.setPrice(rs.getBigDecimal("PRICE"));
line.setQuantity(rs.getBigDecimal("QUANTITY"));
partialResult.getLines().add(line);
return partialResult;
}
/** Returns true if the current record has the same invoice ID of the previous ones. **/
@Override
protected boolean isRelated(ResultSet rs, Invoice partialResult) throws SQLException {
return partialResult.getInvId().equals(rs.getBigDecimal("INVID"));
}
}
最后注意事项:我在JdbcCursorItemReader
的自定义子类中使用CollectingRowMapper
和AbstractCollectingRowMapper
主要使用Spring Batch:我在another answer中描述了此解决方案。使用Spring Batch,您可以在获得下一个相关行之前处理每组相关行,这样您就可以避免加载可能很大的整个查询结果。
答案 3 :(得分:0)
您可以简单使用此库-SimpleFlatMapper已解决了该问题。您需要做的就是使用ResultSetExtractor
创建一个JdbcTemplateMapperFactory
。
import org.simpleflatmapper.jdbc.spring.JdbcTemplateMapperFactory;
private final ResultSetExtractor<List<Invoice>> resultSetExtractor =
JdbcTemplateMapperFactory
.newInstance()
.addKeys("id") // the column name you expect the invoice id to be on
.newResultSetExtractor(Invoice.class);
String query = "SELECT * FROM INVOICE inv JOIN INVOICE_LINE line on inv.id = line.invoice_id"
List<Invoice> results = jdbcTemplate.query(query, resultSetExtractor);
将此依赖项添加到pom.xml
<dependency>
<groupId>org.simpleflatmapper</groupId>
<artifactId>sfm-springjdbc</artifactId>
<version>8.2.1</version>
</dependency>
这里有一篇文章可供参考-https://arnaudroger.github.io/blog/2017/06/13/jdbc-template-one-to-many.html