schizophrenicmaniac commented on PR #40309: URL: https://github.com/apache/shardingsphere/pull/40309#issuecomment-6384356040
@terrymanu Thanks, both are fixed in the latest commit. 1. ShardingResultMergerEngine now uses a new ShardingDMLResultMerger for an INSERT with RETURNING into a sharding table. It iterates over the results of every route instead of keeping only the first one. I limited it to sharding tables because an INSERT into a broadcast table runs on every data source and would otherwise return each row several times. ShardingDMLResultMergerTest merges two backend results and checks that the rows from both come back, and ShardingResultMergerEngineTest covers picking the new merger. 2. Moved putAffectedColumn to right after findAffectedColumns. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
