STEEMSQL - A public SQL database with all blockchain data – Update 7

in steemsql •  2 years ago

SteemSQL is a public MS-SQL database with all the blockchain data in it.

Previous posts:

What’s new?

The hardfork 18.x as brought new operation with it:

  • Vesting shares delegation
  • Reward claim
  • Account creation with delegation
  • Reward sharing with other beneficiaries

These changes have been reflected in the database structure, either with new tables or new fields in existing tables.

Here the changes details

  • Vesting shares delegation
  • Reward claim
  • Account creation with delegation
  • Reward sharing with other beneficiaries

These changes have been reflected in the database structure, either with new tables or new fields in existing tables.

Here the changes in details

New tables

Two new tables have been created to store delegate_vesting_shares and claim_reward_balance transactions. They are respectively named TxDelegateVestingShares and TxClaimRewardBalances

Changes in TxAccountCreates table

A new field delegation has been added in the table to support the account_create_with_delegation transactions.
These transactions will not be stored in a separate table.
The delegation field value will be set to zero for classic account_create transactions

Changes in Comments table

Two new fields beneficiaries and reblogged_by have been added to the Comments table to reflect the changes in the get_comment API



Thanks for reading!


All payout from this post will be dedicated keep SteemSQL running. Thanks for your support.

Support me and my work as a witness by voting for me here!

You like this post, do not forget to upvote or follow me or resteem

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Hi @arcange

As always, thanks so much for SteemSQL, a great tool!

I was wondering if you had a query to find 'active' delegations?

I see an entry in TxDelegateVestingShares for vesting_shares = 0.0000, but I can't work out how to use this to exclude 'old' delegations - particularly if a delegation has been ended, and then re-issued to the same user.

Any help or clues would be greatly appreciated!