You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first image shows the deployment of the go-version basic chaincode in testnetwork. You can see that the command is "chaincode peer. add..," and the query is correct.
The second image shows the deployment of the Java-version basic chaincode after the contract upgrade, and you can see that the command is "/root/chaincode jav...".
At this point, there will be problems when querying all assets, as seen in image 3.
But the data is still in the database, as seen in image 4.
The answer I received is:
This is probably because go-version chaincode and Java-version chaincode use different key names in Asset's JSON format.
The text was updated successfully, but these errors were encountered:
The first image shows the deployment of the go-version basic chaincode in testnetwork. You can see that the command is "chaincode peer. add..," and the query is correct.
The second image shows the deployment of the Java-version basic chaincode after the contract upgrade, and you can see that the command is "/root/chaincode jav...".
At this point, there will be problems when querying all assets, as seen in image 3.
But the data is still in the database, as seen in image 4.
The answer I received is:
This is probably because go-version chaincode and Java-version chaincode use different key names in Asset's JSON format.
The text was updated successfully, but these errors were encountered: