forked from Qortal/qortal
Fixed bug which prevented the "reduced name" from being updated in UPDATE_NAME transactions.
Updating a name was incorrectly leaving the existing "reduced name" intact. Thanks to Qortal user @MyBestBet for reporting this bug.
This commit is contained in:
parent
d600a54034
commit
cc65a7cd11
@ -78,9 +78,10 @@ public class Name {
|
||||
// Set name's last-updated timestamp
|
||||
this.nameData.setUpdated(updateNameTransactionData.getTimestamp());
|
||||
|
||||
// Update name and data where appropriate
|
||||
// Update name, reduced name, and data where appropriate
|
||||
if (!updateNameTransactionData.getNewName().isEmpty()) {
|
||||
this.nameData.setName(updateNameTransactionData.getNewName());
|
||||
this.nameData.setReducedName(updateNameTransactionData.getReducedNewName());
|
||||
|
||||
// If we're changing the name, we need to delete old entry
|
||||
this.repository.getNameRepository().delete(updateNameTransactionData.getName());
|
||||
@ -106,6 +107,9 @@ public class Name {
|
||||
// We can find previous 'name' from update transaction
|
||||
this.nameData.setName(updateNameTransactionData.getName());
|
||||
|
||||
// We can derive the previous 'reduced name' from the previous name
|
||||
this.nameData.setReducedName(Unicode.sanitize(updateNameTransactionData.getName()));
|
||||
|
||||
// We might need to hunt for previous data value
|
||||
if (!updateNameTransactionData.getNewData().isEmpty())
|
||||
this.nameData.setData(findPreviousData(nameReference));
|
||||
|
Loading…
x
Reference in New Issue
Block a user