1.5.0 (Not Apache Release)

Milestones

1. The new SQL parsing module removes the dependence on Druid. We only need to parse the sharding context, and adopt a "semi understanding" concept for SQL to further improve performance and compatibility, and reduce code complexity
2. The new SQL rewrite module adds an optimized rewrite module
3. The new SQL merge module is rebuilt into 3 merging engines: streaming, memory and decorator

New Features

1. Support Oracle, SQLServer and PostgreSQL
2. Non functional sub-query support

Enhancements

1. ISSUE #256 Configurable display sharding execute to SQL log
2. ISSUE #291 Processing SQL use stream mode that contains only GroupBy

Changes

1. Simplify the distributed self increasing sequence. Each table is supported by simplifying a multiple self increasing sequence to a single table supporting only a single distributed self increasing sequence, and no longer supporting workerID settings through environment variables
2. Remove support for OR

Bug Fixes

1. ISSUE #239 LIMIT routes to multiple query result sets. If there is only one result set that is not empty, the result of paging is incorrect
2. ISSUE #263 Sharding and logical table configuration can be case insensitive
3. ISSUE #292 When the memory mode handles GROUP BY statement, if there is paging information, it needs to be rewritten
4. ISSUE #295 LIMIT 0 does not filter the result set according to paging restrictions

1.5.0.M3 (Not Apache Release)

Milestones

1. The new SQL merge module is rebuilt into 3 merging engines: streaming, memory and decorator

Bug Fixes

1. ISSUE #292 When the memory mode handles GROUP BY statement, if there is paging information, it needs to be rewritten

1.5.0.M2 (Not Apache Release)

Enhancements

1. Non functional sub-query support
2. Support Paging for Oracle and SQLServer
3. Support display of SQL execution

Bug Fixes

1. ISSUE #239 LIMIT routes to multiple query result sets. If there is only one result set that is not empty, the result of paging is incorrect
2. ISSUE #263 Sharding and logical table configuration can be case insensitive

1.5.0.M1 (Not Apache Release)

Milestones

1. The new SQL parsing module removes the dependence on Druid. We only need to parse the sharding context, and adopt a "semi understanding" concept for SQL to further improve performance and compatibility, and reduce code complexity
2. Support Oracle, SQLServer and PostgreSQL
3. Simplify the distributed self increasing sequence. Each table is supported by simplifying a multiple self increasing sequence to a single table supporting only a single distributed self increasing sequence, and no longer supporting workerID settings through environment variables

Not Support Items

1. Do not support Paging for Oracle and SQLServer
2. Remove support for OR

Developing

1. Refine ShardingRule, each ShardingRule only support single TableRule
2. BindingTableRule enhanced, each TableRule can support BindingTableRule with multiple different sharding strategies
3. Support sub-query
4. Support OR
5. Support Paging for Oracle and SQLServer
6. Support inline sharding strategy

1.4.2 (Not Apache Release)

Enhancements

1. ISSUE #219 Thread performance optimization
2. ISSUE #215 Aggregated result set of stream sort StreamingOrderByReducerResultSet performance optimization
3. ISSUE #161 When the result sets are merged, heap sort can be used to improve performance

Bug Fixes

1. ISSUE #212 More meaningful hints for missing data source rules
2. ISSUE #214 table_name.column_name in (?,?) in WHERE can't parser expression
3. ISSUE #180 Batch execution of Update return inaccuracy
4. ISSUE #225 The last character of automatic generation of Id is not 0

1.4.1 (Not Apache Release)

Enhancements

1. ISSUE #191 Generating KeyGenerator of workerId based on IP of host
2. ISSUE #192 Get workerId's KeyGenerator based on HOSTNAME's digital suffix
3. ISSUE #210 Routing to single library and single table to remove supplementary SQL statement fragments

Bug Fixes

1. ISSUE #194 Some component exceptions in the close method of Connection, Statement, Resultset and other interfaces cause the close method of another component to be not invoked
2. ISSUE #199 Sharding and reuse PreparedStatement object cause route error
3. ISSUE #201 Event transmission missing before batch operation execution
4. ISSUE #203 Merge events sent by the batch operation
5. ISSUE #209 Parallel execution of multiple limit queries leads to IndexOutOfBoundsException

1.4.0 (Not Apache Release)

Enhancements

Automatic generation key implementation, including

1. ISSUE #162 Implementation of distributed primary key algorithm
2. ISSUE #163 Acquisition of a self increasing sequence of JDBC interfaces
3. ISSUE #171 Sharding-jdbc-core coordination automatic generation sequence transformation
4. ISSUE #172 The configuration of YAML and Spring supports the self increasing sequence

Bug Fixes

1. ISSUE #176 The wasNull flag of AbstractMemoryResultSet is not reset in time

1.3.3 (Not Apache Release)

Enhancements

1. ISSUE #59 PreparedStatement can call the correct underlying set method according to the parameter type when setting parameters

Bug Fixes

1. ISSUE #149 When INSERT IGNORE INTO, if the data is duplicated, the value returned to -1 when ignored, and it should be returned to 0
2. ISSUE #118 In the same thread, DQL is executed first, then DML is executed, and DML operation is executed from the slave database
3. ISSUE #122 In cases where connections are not available (such as network interruption), transactions should be interrupted rather than retry
4. ISSUE #152 PreparedStatement's cache causes an array out of bound
5. ISSUE #150 With the latest SQLServer jdbc driver compatibility problem, Product Name should be changed from SQLServer to Microsoft SQL Server
6. ISSUE #166 Druid data source stat filter multi-thread error reporting should be added to database connection level synchronization

1.3.2 (Not Apache Release)

Enhancements

1. ISSUE #79 Optimizes limit for only one target table, does not modify limit offset

Bug Fixes

1. ISSUE #36 ShardingPreparedStatement cannot set parameters repeatedly
2. ISSUE #114 When ShardingPreparedStatement performs batch tasks, it repeatedly analyzes SQL and leads to OOM
3. ISSUE #33 According to the MySQL document, queries similar to limit 100 and -1 format are not supported
4. ISSUE #124 The return value of com.dangdang.ddframe.rdb.sharding.jdbc.adapter.AbstractStatementAdapter.getUpdateCount does not conform to the JDBC specification
5. ISSUE #141 Multi-thread executor parameter setting failure

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