1.3.1 (Not Apache Release)

Enhancements

1. ISSUE #91 Open support for Statement.getGeneratedKeys can return the original database self increase primary key
2. ISSUE #92 Query DQL statement event sending

Bug Fixes

1. ISSUE #89 Use read-write separation with sharding hint leads to conflict
2. ISSUE #95 Write operations in the same thread are read from the master database changed to the same thread and within the same connection

1.3.0 (Not Apache Release)

New Features

1. ISSUE #85 Read-write separation

Enhancements

1. ISSUE #82 TableRule can import the dataSourceName attribute to specify the data source corresponding to the TableRule
2. ISSUE #88 Release restrictions on other databases, support standard SQL, do not support personalized paging statements

Bug Fixes

1. ISSUE #81 Associative table query uses OR query condition to resolve the result exceptions

1.2.1 (Not Apache Release)

Refactor

1. ISSUE #60 API adjust, remove ShardingDataSource, use factory instead
2. ISSUE #76 ShardingRule and TableRule change to Builder pattern
3. ISSUE #77 ShardingRule and TableRule change to Builder pattern

Enhancements

1. ISSUE #61 Add the logical table name to the ShardingValue class
2. ISSUE #66 Statement on the JDBC tier supports get/set MaxFieldSize, MaxRows and QueryTimeout
3. ISSUE #72 Batch inserts supporting select union all
4. ISSUE #78 Simplifying sharding only configuration, without configuring logical table and real table correspondence
5. ISSUE #80 Simplifying the configuration that does not sharding, specifying the default data source, do not need configure TableRule

Bug Fixes

1. ISSUE #63 No table name or table alias is added to the ORDER BY and GROUP BY derivation columns
2. ISSUE #65 Performance enhancement for parsing condition context
3. ISSUE #67 The soft transaction log cannot be deleted when routed to multiple tables
4. ISSUE #71 Routing single sharding key by OFFSET of LIMIT error
5. ISSUE #75 MemoryTransactionLogStorage retry times update concurrency problem

1.2.0 (Not Apache Release)

New Features

1. ISSUE #53 The relationship between the real table and the logical table is not configured, and the real table is dynamically calculated by the sharding algorithm
2. ISSUE #58 Soft transaction: the initial version of the best effort type

Refactor

1. ISSUE #49 Adjust the property configuration
2. ISSUE #51 Refector of Hint interface

Bug Fixes

1. ISSUE #43 The yaml file contains Chinese, and the operating system mode is not UTF-8 encoding, resulting in yaml can not be parsed
2. ISSUE #48 Yaml file is not closed after reading
3. ISSUE #57 At the analytic level, we can identify sub queries to ensure that the behavior of supplementary columns can be accurately positioned

1.1.0 (Not Apache Release)

New Features

1. ISSUE #40 Support YAML configuration
2. ISSUE #41 Support Spring namespace configuration
3. ISSUE #42 Support inline expression configuration

Bug Fixes

1. ISSUE #25 The problem of repeated results will appear under the OR expression

1.0.1 (Not Apache Release)

Enhancements

1. ISSUE #39 Support the use of Hint method to register the key value to SQL routing

Bug Fixes

1. ISSUE #11 The count function returns incorrectly without aliases
2. ISSUE #13 The Insert statement does not write column names or write column names but column names do not contain sharding fields, occur broadcast route
3. ISSUE #16 For now a new connection pool is executed every time SQL is executed. Instead, each ShardingDataSource object should be changed to share a pool
4. ISSUE #18 When query Count, getObject() throws Exception: Unsupported data type: Object
5. ISSUE #19 In SUM and AVG functions, merger is not executed if aliases are not added, and null pointer exception fired if aliases are added
6. ISSUE #38 The compatibility between JPA and Sharding-JDBC. JPA automatically add the column aliases of SELECT, resulting in ORDER BY obtaining ResultSet data only by aliases rather than column names

1.0.0 (Not Apache Release)

• Initial version