You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new competition_auctions table is being introduced with PR #2980. While this PR will populate new entries, we also need to backfill historical data, as the necessary information already exists in other tables. This will allow us to drop other tables.
Details
Populate the auctions table using existing data from the following sources:
auction_id – from solver_competition table
block – from solver_competition table field auctionStartBlock
deadline – from settlement_scores table; if missing, set to 0 or use the value of block
order_uids – from solver_competition or auction_orders table
prices – from solver_competition or auction_prices table
surplus_capturing_jit_order_owners – from surplus_capturing_jit_order_owners table
The text was updated successfully, but these errors were encountered:
Executed manually on all staging and production databases.
Few hiccups on production databases where we had gaps due to failure to save auctions caused by #3088
Another hiccup was on mainnet production for auction 3278851 that somehow has solver_competition.json = null. For this one, I think it's fine to not have entry in competition_auctions.
Background
A new
competition_auctions
table is being introduced with PR #2980. While this PR will populate new entries, we also need to backfill historical data, as the necessary information already exists in other tables. This will allow us to drop other tables.Details
Populate the auctions table using existing data from the following sources:
auction_id – from
solver_competition
tableblock – from
solver_competition
table fieldauctionStartBlock
deadline – from
settlement_scores
table; if missing, set to 0 or use the value of blockorder_uids – from
solver_competition
orauction_orders
tableprices – from
solver_competition
orauction_prices
tablesurplus_capturing_jit_order_owners – from
surplus_capturing_jit_order_owners
tableThe text was updated successfully, but these errors were encountered: