HiveSQL Upate - Database maintenance and new Account Recovery Tables
As you know, the account recovery process is something I have [worked](/hive-139531/@arcange/hive-account-recovery-major-update-and-new-user-interface) on and [written](/hive-139531/@arcange/account-recovery-about-trusting-and-not-being-trusted) a lot about recently.
This allowed me to better understand the related transactions recorded in the blockchain. I also noticed that the related tables in HiveSQL were not that well organized (some early days errors)
So I took advantage of the HiveSQL reorganization work that I am currently carrying out to make some modifications.
### What changed?
* The table `TxAccountChangeRecovers` has been renamed to `TxAccountRecoveryChanges`
* The content of the table `TxAccountRecovers` has been split into `TxAccountRecoveryRequests` and `TxAccountRecoveryConfirms`.
Therefore, we now have three new tables available:
**TxAccountRecoveryChanges**
This table contains operations broadcasted to the blockchain when users want to change their Recovery Account.
|Column|Description|
|-|-|
|account_to_recover|the account that wants to change its Recovery Account|
|new_recovery_account|the new Recovery Account|
**TxAccountRecoveryRequests**
This operation is broadcasted to the blockchain by the Account Recovery of an account that has been hacked to initiate the recovery process
|Column|Description|
|-|-|
|recovery_account|username of the Recovery Account|
|account_to_recover|username of the account to recover|
|new_owner_authority|new public owner key provided by the account to recover to the recovery account|
**TxAccountRecoveryConfirms**
This table contains operations broadcasted to the blockchain by the hacked account's owner to confirm the account recovery request sent by its Recovery Account.
|Column|Description|
|-|-|
|account_to_recover|username of the account to recover|
|new_owner_authority|new public owner key provided by the account to recover to the recovery account|
|recent_owner_authority|a public owner key of the account to recover before it was last changed|
## What's next?
This first change should make it easier to find information relating to the account recovery process.
As indicated at the beginning of this post, I have embarked on a work of reorganizing and improving the database. So expect to see more posts on this subject in the coming days.
## Support
If you have any questions or remarks, support is provided on the [HiveSQL Discord Channel](https://discord.gg/kyEFDfT).
Thank you for reading.
---
**Let's keep HiveSQL free to use - Support its proposals**!
|HiveSQL|HiveBuzz|
|-|-|
|[Vote for the proposal on PeakD](https://peakd.com/me/proposals/138)
[Vote for the proposal on Ecency](https://ecency.com/proposals/138)
[Vote for the proposal using HiveSigner](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22138%22%5D&approve=true)|[Vote for the proposal on PeakD](https://peakd.com/me/proposals/147)
[Vote for the proposal on Ecency](https://ecency.com/proposals/147)
[Vote for the proposal using HiveSigner](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22147%22%5D&approve=true)| ---
### Check out my apps and services
### [Vote for me as a witness ](https://hivesigner.com/sign/account-witness-vote?witness=arcange&approve=1)
[Vote for the proposal on Ecency](https://ecency.com/proposals/138)
[Vote for the proposal using HiveSigner](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22138%22%5D&approve=true)|[Vote for the proposal on PeakD](https://peakd.com/me/proposals/147)
[Vote for the proposal on Ecency](https://ecency.com/proposals/147)
[Vote for the proposal using HiveSigner](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22147%22%5D&approve=true)| ---
See: HiveSQL Upate - Database maintenance and new Account Recovery Tables by @arcange