HiveSQL Upate - Changes to the Internal Market tables

I am actively continuing the work of reorganizing the HiveSQL database that I started a few days ago. Lately, I tackled the tables related to the internal market.

There are two operations associated with it: the creation of orders (buy or sell) and their cancellation. However, until now, these two operations were grouped together in a single table, which could cause confusion, but also wasted storage resources.

What changed?

  • A new TxLimitOrdersCancels table has been created and cancel orders have been moved from the table TxLimitOrders to TxLimitOrdersCancels
  • The table TxLimitOrders (purged from the cancel orders) has been renamed to TxLimitOrdersCreates

Therefore, we now have two new tables available:

TxLimitOrdersCreates

This table contains operations broadcasted to the blockchain when users want to buy or sell assets on the internal market.

ColumnDescription
owneraccount who filled a limit order
orderidan order ID defined by the owner. It must be unique
amount_to_sellamount of asset
amount_to_sell_symbolsymbol of the asset
min_to_receiveThe target asset expected price (limit_order_create operation)
min_to_receive_symbolThe target asset expected symbol (limit_order_create only)
exchange_rateThe target asset expected price (limit_order_create2 operation)
fill_or_killflag to specify if the order should be killed (removed) from the order book if it cannot be filled
expirationexpiration time for the order

TxLimitOrdersCancels

This table contains operations broadcasted to the blockchain when users want to cancel orders created on the internal market.

ColumnDescription
owneraccount who filled a limit order
orderidan order ID defined by the owner

Support

If you have any questions or remarks, support is provided on the HiveSQL Discord Channel.

Thank you for reading.


Let's keep HiveSQL free to use - Support its proposals!

HiveSQLHiveBuzz
Vote for the proposal on PeakD
Vote for the proposal on Ecency
Vote for the proposal using HiveSigner
Vote for the proposal on PeakD
Vote for the proposal on Ecency
Vote for the proposal using HiveSigner

Check out my apps and services


Vote for me as a witness

H2
H3
H4
3 columns
2 columns
1 column
8 Comments
Ecency