推荐使用ParameterizedRowMapper或者RowMapper
我对 Spring JDBC 非常陌生，正在处理给定的任务，查看我的队友已经使用 RowMapper 的代码，但我在进行一些谷歌搜索时看到一些教程正在使用 ParameterizedRowMapper ，所以我想知道是否有任何好处或者使用其中一种而不是另一种的良好实践以及您背后的技术思想......
谢谢。
I am very new to Spring JDBC and working on a given task, looking at the codes we already have my teammates have used RowMapper, but I was doing some Googling and saw some tutorials are using ParameterizedRowMapper , so I was wondering if there is any benefit or good practice in using one rather than the other one and your technical thoughts behind that...
thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
直接来自 javadoc参数化行映射器：
Right from the javadoc of ParameterizedRowMapper:
在 Spring 3.0 之前，大多数 API 不使用泛型，因为 Java 1.5 不是必需的。因此，出现了不支持泛型的 RowMapper 和通过扩展 RowMapper 并添加泛型参数来支持泛型的 ParameterizedRowMapper。从 Spring 3.0 开始，大多数 API 都已更新以支持泛型。如果您实际查看 ParameterizedRowMapper 的当前（3.0 或更高版本）定义，您会发现它只是简单地扩展了 RowMapper，并且没有向定义添加任何内容以实现向后兼容性。因此，您几乎可以使用参数化或非参数化的 RowMapper，而无需使用 ParameterizedRowMapper。
Prior to Spring 3.0, most APIs did not use generics because Java 1.5 wasn't a requirement. As a result, there was a RowMapper, that didn't support generics and ParameterizedRowMapper that did support generics by extending RowMapper and adding the generic parameter. As of Spring 3.0, most APIs were updated to support generics. If you actually look at the current (3.0 or greater) definition of ParameterizedRowMapper, it just simply extends RowMapper and adds nothing to the definition to allow for backward compatibility. Therefore, you can pretty much use RowMapper either parameterized or not and no need to use ParameterizedRowMapper.