Sachiko Yoshihama

@corecode Right, we can implement a kind of "export" and "import" as workaround. But as you pointed out, it will be very inefficient. I think it will be more efficient...

@muralisrini I agree with you. I think it is a simple and practical approach.

Hi @angrbrd So I think the current design assumes that when a user performed enrolment on one peer, the peer is trusted by the user, and maintains the security tokens...

Sorry, more precisely, the first GetRows() crashes when the table size > 100. PR https://github.com/hyperledger/fabric/pull/2013 tries to fix this issue but insufficient.

@muralisrini Thank you, it worked well. I confirmed it fixed the problem.

@muralisrini I tested again... ok, actually, the PR for GetRows() did not completely fix the problem. I double checked, and it returned only 136 rows when there are 200 rows...

@bren3582 I am concerned with the backward-compatibility problem to replace GetRows() in master with GetRows2(). Especially there is a risk that people use GetRows2() without knowing that the chaincode needs...