2.2.5 (September 14th, 2017)

Task

• [DB-17] - Use ConnId commons

Improvement

• [DB-18] - Pass connector configuration to scripts

2.2.4 (June 1st, 2016)

Bug

• [DB-15] - Error messages not shown during configuration validation

Improvement

• [DB-16] - Add support for pagination API

...

• [DB-12] - setAutoCommit exceptions thrown if the JDBC driver used doesn't support the call
• [DB-14] - NameNotFoundException using Datasource Path property

Improvement

• [DB-13] - Allow usage of System properties in script file names

...

• [DB-9] - LatestSyncToken retrieving fails in case of changelog column of type timestamp on oracle
• [DB-11] - Execute query doesn't return accountId attribute

Improvement

• [DB-10] - Permit changelog column into search/sync result

...

2.2.0 (October 23rd, 2014)

Task

• [DB-6] - Upgrade to ConnId 1.4.0.0

2.1.7 (June 25th, 2014)

Improvement

• [DB-5] - Add support for a "HASHED_PASSWORD" attribute

2.1.4.2 (June 16th, 2014)

Task

• [DB-4] - Backport scripted sql connector onto framework 1.3.2

...

This release does not contain relevant changes compared to 2.1.5, but features the new Scripted SQL connector.

Task

• [DB-3] - Provide Scripted SQL documentation

...

This release backports 2.1.5 features for usage with ConnId 1.3.2.

Task

• [DB-2] - Backport 2.1.5 features to ConnId base 1.3.2

2.1.5 (March 18th, 2013)

Improvement

• [#52] - DBTable and password encoding support

Task

• [DB-1] - Fix mandatory and default values information

...

1. Removed mandatory constraint onto password cipher algorithm field (#36).
2. Given the possibility to force password encoding to all upper/lower cases (#41).
3. Fixed "Password cipher algorithm" configuration parameter inconsistency (#50).

2.1 (January 12th, 2012)

With great pleasure we announce the availability of the new Database Table connector's 2.1 release.

The most important new features are:

1. Possibility to cipher the password using MD5, AES, SHA-1, SHA-256 or a custom algorithm implementation (#23).
2. Possibility to specify a cipher key to decrypt password encrypted by using a reversible algorithm (AES or a custom one).
3. Possibility to choose to retrieve password by default during sync or search query.