Releases: JSqlServerBulkInsert/JSqlServerBulkInsert
Releases · JSqlServerBulkInsert/JSqlServerBulkInsert
5.1.0
4.0.1
4.0.0
This commit added:
- Database metadata validation to prevent confusion like in Issue #15, because the
SqlServerBulkCopy
requires all columns to explicitly mapped. An exception will be thrown, if the destination schema and source mapping do not match. A section has been added to the README, so with the validation and README the behavior should be a little more predictable. - The columns now get reordered based on the metadata of the destination table. The
SqlServerBulkCopy
requires all columns to be exactely in the same order as in the database, so we reorder them before starting the bulk insert from the stream.
The methods for primitive type mapping have been renamed to mapBooleanPrimitive
, so the IDE and JVM do not confuse the lambda methods and thus making it easier to do the mapping for empty / auto-generated columns. This is a breaking change, so the Major Release version has been increased to 4.0.0.
3.0.0
2.0.0
This release features a revamped API surface authored by @bytefish. In short, the mapping API has been cleaned up to clarify the specific column types that are being mapped to in Sql Server. In addition, new methods have been added to reduce/eliminate common boxing scenarios involving primitives, similar to PgBulkInsert/PgBulkInsert#27. Finally, the internals have been overhauled, which is described in more detail in #10.
🚀 Features
- new 2.0 API surface @bytefish (#11)
- ability to map UTC nano long to separate date/time columns in db @vslee (#9)
🎯 Dependency changes
- mssql-jdbc dependency to
7.2.2.jre8