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 tableTxLimitOrders
toTxLimitOrdersCancels
- The table
TxLimitOrders
(purged from the cancel orders) has been renamed toTxLimitOrdersCreates
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.
Column | Description |
---|---|
owner | account who filled a limit order |
orderid | an order ID defined by the owner. It must be unique |
amount_to_sell | amount of asset |
amount_to_sell_symbol | symbol of the asset |
min_to_receive | The target asset expected price (limit_order_create operation) |
min_to_receive_symbol | The target asset expected symbol (limit_order_create only) |
exchange_rate | The target asset expected price (limit_order_create2 operation) |
fill_or_kill | flag to specify if the order should be killed (removed) from the order book if it cannot be filled |
expiration | expiration time for the order |
TxLimitOrdersCancels
This table contains operations broadcasted to the blockchain when users want to cancel orders created on the internal market.
Column | Description |
---|---|
owner | account who filled a limit order |
orderid | an 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!