I have merged all my 5.0.0 PRs to 4.0.1. I suggest all committers check theirs to avoid miss.
5.0.0 #3861, PostgreSQL Proxy read parameters error in all types except String #3968, Ambiguous description of COM_STMT_EXECUTE in MySQL protocol #4042, Use the two-stage parsing strategy recall travis #4182, ignore showLike context in show columns 4.0.1 #3861, carry pr#3863 from dev to 4.0.1 #3968, carry pr#3969 from dev to 4.0.1 #4042, carry pr#4045 to 4.0.1 (kimmking) add travis config #4203 #4182, ignore showLike context in show columns -- Zhang Yonglun Apache ShardingSphere zhaojun <[email protected]> 于2020年2月9日周日 下午3:44写道： > Hi, ShardingSphere community, > > I’d like to be the release manager of 4.0.1 version. > We have done some bug fixes and performance optimization in past month > based on 4.0.0. > If there is no other requirement, I think we can start to release 4.0.1 > recently. > > > ## Bug fixes > > 3975 oracle insert SQL could not work in encrypt mode > 3997 proxy for PostgreSQL decode parameters error in all types except > String > 4022 none sharding strategy could not config in spring-boot > 4052 plain column could not get from resultSet in sharding-encrypt mode > 4173 wasNull field was wrong in GroupByStreamMergeResult > > > ## Enhancement > > 3956 using guava cache to improve parsing performance > 4004 optimize COM_STM_EXECUTE of MySQL to support sysbench > 4054 optimize antlr performance using two-stage parsing strategy > 4205 add class filter constructor to restrict the illegal class from YAML > > Thanks to these contributors for their code commits. > - tuohai666, xiyelife, SteNicholas, KomachiSion, beckhampu, plazmdk > > Any other task missing here? Please feel free to let me know. > > ------------------ > Zhao Jun (cherrylzhao) > Apache ShardingSphere & ServiceComb
