2.1.0

• No change at all in DbSetup itself. But a new Kotlin module is available. Read the user guide to understand why and how to use it. DbSetup's version has been incremented anyway in order for both modules to have the same version.

2.0.0

• Feature #51: Support Java 8 Date/Time. DbSetup now requires Java 8. People still running on Java 7 or Java 6 should keep using DbSetup 1.x. DbSetup now supports the following types from the java.time package: Instant, LocalDate, LocalDateTime, LocalTime, OffsetDateTime, OffsetTime and ZonedDateTime.

1.6.0

• Feature #41: Allow inserting the same values multiple times, without having to use a loop. See the user guide for an example.
• Fix #43: Documentation typos

1.5.0

• Enhancement for #35: Add a toString() method to Insert.Builder
• Enhancement for #36: Make DbSetup OSGI-ready by adding OSGI entries in the manifest of the jar.

1.4.0

• Enhancement for #33: Allows getting the number of rows inserted by an Insert operation.

1.3.1

• Fix for #31: H2 doesn't seem to support passing a BigInteger to setObject(). Passing a String to a column of type BIGINT transformed the String into a BigInteger and passed that BigInteger to the prepared statement. This resulted to a strange, misleading error message from H2. Given that JDBC doesn't have official support for BigInteger, the strategy has been reversed: passing a BigInteger transforms the BigInteger to a String and this String is passed to the prepared statement. See the javadoc of Binders.integerBinder() for details.

1.3.0

• There is no need to call useMetadata(false) for every insert with databases like Oracle and MySQL which don't support parameter metadata. In previous versions, a SQLException was thrown and, if metadata usage was turned off, the default binder was used. Now the active BinderConfiguration can catch the exception and return the binder it wants. The default BinderConfiguration does that and returns the default binder.
• The default binder has been improved. It now inspects the type of the value to bind. If it's a java.util.Date or a java.util.Calendar, the bound value is a java.sql.Timestamp. If it's an enum, the name of the enum is bound.

1.2.0

• Add the possibility to specify the column names of every cell of inserted rows.

1.1.0

• Add with() factory methods to DataSourceDestination and DriverManagerDestination. Thanks to Alexis Hassler.
• Start using semantic versioning. For the record, this release is backward-compatible with 1.0 and 1.0-RC1.

1.0

• Add support for generated values in Insert operations. See the javadoc for Insert.Builder.withGeneratedValue() and for the classes in the package com/ninja_squad/dbsetup/generator. Thanks to Gaetan Zoritchak for this suggested evolution and his feedbacks

1.0-RC1

Initial release

---