https://github.com/marschall/jdbctemplate-ng

a new take on JdbcTemplate
https://github.com/marschall/jdbctemplate-ng

Last synced: 3 months ago
JSON representation

a new take on JdbcTemplate

• Host: GitHub
• URL: https://github.com/marschall/jdbctemplate-ng
• Owner: marschall
• Created: 2018-01-14T12:23:05.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-08-29T12:51:21.000Z (over 1 year ago)
• Last Synced: 2025-01-16T02:44:52.358Z (4 months ago)
• Language: Java
• Size: 114 KB
• Stars: 2
• Watchers: 3
• Forks: 0
• Open Issues: 5
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
JdbcTemplateNg

==============

A new take on JdbcTemplate.

This project has the following goals:

- support Optional

- reduce the number of methods on JdbcOperations

- native support named parameters (Oracle, IBM DB2)

additional features:

- more control over return type by use of a collector

- statement customizer allows to set fetch size without having to create a prepared statement creator

- large update support

non-goals

features not supported:

- java.util.Date <-> java.sql.Timestamp and java.util.Calendar <-> java.sql.Timestamp type conversions, use JSR-310 datatypes

- work around JDBC driver bugs

- consider JDBC metadata

- jdbc type support

- rownum in RowMapper

- stored procedures

TODO

====

- tests for failed updates

- unprepared statement for statements without bind parameters

???

===

- naming: query().collectTo...

- naming: update().for...

- naming: batchUpdate().forGeneratedKeysAndFailedUpdates is bad, something with generated keys and callback

- naming: JdbcTemplate.(batch)UpdateForGeneratedKeys()

- should #binding support a collection as an argument, especially for batch updates

- case insensitive map, map contract, keySet, equals contract

- should binding happen at the end so that operations can be cached? PreparedStatementSetter would have to take arguments