HiveSQL Update - New proposals tables
There has been a lot of discussion about the proposals recently, especially about the proposals relating to the @hbdstabilizer project, but also following the de-funding and re-funding of the HiveSQL proposal.
That's why, over the last few days, I've been working on proposal data, some of which was still missing in HiveSQL.
While preparing this post, I realized that there was already a whole series of updates that I had already done in the database but for which I had not published a post yet. This is what happens when you are more of a worker than a blogger. Now is the time to rebalance this a bit.
What's new?
New tables
Several new table have been added to the database:
| Table name | Description |
|---|---|
| TxProposalCreates | Creation of a new proposal |
| TxProposalUpdates | Update of the data of a proposal |
| TxProposalRemoves | Removal of a proposal |
| TxProposalVoteUpdates | Vote and Unvote performed by user on one or several proposals |
The names of the columns in the tables and their purpose are self-explanatory enough that I don't have to list them here. This will be added to the documentation I will release soon.
The above tables are "transactional tables", meaning a new row is created each time a new transaction is broadcasted to the blockchain.
I also created two additional tables:
| Table name | Description |
|---|---|
| Proposals | List of ALL proposal and their data (including deleted ones) |
| ProposalsApprovals | List of the proposals that are approved by each user |
The two above tables are "state tables", meaning they reflect the result of the transactions that have been broadcasted to the blockchain.
The big advantage of these last two tables is that they keep the data relating to the proposal which are deleted or expired. This is information that Hive APIs currently do not provide!
Steem columns removed
Until now, several tables of the database still contained certain columns relating to the other blockchain (whose name must not be said), this in order to not allow Hive applications previously working with SteemSQL to update them with complete peace of mind when we forked.
As it has been a year since we split up, it was time to draw the final line and remove these no longer needed columns. It is therefore now officially done.
Support the Hive proposal
Vote for the proposal on PeakD
Vote for the proposal on Ecency
Vote for the proposal using HiveSigner
If you have any questions or remarks, support is provided on the HiveSQL Discord Channel.
