📰 2023-06-02: Weekly Prophet! #3462
andrewhong5297
announced in
Prophet (Weekly Updates)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is your weekly summary of 11 PRs merged from 11 wizards. Great job everyone! 🎉
We had 11 added models 🟢 and 29 modified models 🟠 for 13 Sectors.
SECTOR: labels
toggle to see all model updates
MODEL: labels_balancer_v2_gauges_arbitrum.sql
🟠 Modified by:
🔧 PR: #3427, Balancer arbitrum gauges label hotfix
🧙 Author: @hildobby on 2023-05-26
📝 Summary: The SQL model adds a distinct select statement to retrieve data from two different sources. The first source is joined with a left join and the second one with an inner join. Both joins are connected to another table using their respective addresses, and the results of both selects are combined using UNION ALL.
SECTOR: tokens
toggle to see all model updates
MODEL: tokens_avalanche_c_erc20.sql
🟠 Modified by:
🔧 PR: #3420, Adding DEUS token
🧙 Author: @discochuck on 2023-05-26
📝 Summary: The token symbol 'DEUS' was added to the SQL model.
MODEL: tokens_ethereum_erc20.sql
🟠 Modified by:
🔧 PR: #3422, [ERC20] [Easy] Add new & missing tokens
🧙 Author: @gentrexha on 2023-05-26
📝 Summary: [changes too large] The model tokens_ethereum_erc20.sql was modified.
SECTOR: prices
toggle to see all model updates
MODEL: prices_ethereum_tokens.sql
🟠 Modified by:
🔧 PR: #3430, Bad price feed: PRXY and RNBW (ethereum)
🧙 Author: @grkhr on 2023-05-26
📝 Summary: Tokens added: None Tokens removed: PRXY, RNBW
SECTOR: lido
toggle to see all model updates
MODEL: lido_liquidity_optimism_kyberswap_pools.sql
🟢 Added by:
🔧 PR: #3407, wsteth kyber pools arbitrum/optimism
🧙 Author: @ppclunghe on 2023-05-26
📝 Summary: [changes too large] The model lido_liquidity_optimism_kyberswap_pools.sql was added.
🟠 Modified by:
🔧 PR: #3407, exclude failing lido model
🧙 Author: @0xRobin on 2023-05-30
📝 Summary: [changes too large] The model lido_liquidity_optimism_kyberswap_pools.sql was modified.
MODEL: lido_liquidity.sql
🟠 Modified by:
🔧 PR: #3407, wsteth kyber pools arbitrum/optimism
🧙 Author: @ppclunghe on 2023-05-26
📝 Summary: In this diff of a dbt SQL model, three references to different liquidity pools have been added. The original reference to the Ethereum Kyberswap pools remains, but now there are also references to the Arbitrum Kyberswap and Optimism Kyberswap pools.
MODEL: lido_liquidity_arbitrum_kyberswap_pools.sql
🟢 Added by:
🔧 PR: #3407, wsteth kyber pools arbitrum/optimism
🧙 Author: @ppclunghe on 2023-05-26
📝 Summary: [changes too large] The model lido_liquidity_arbitrum_kyberswap_pools.sql was added.
SECTOR: dodo
toggle to see all model updates
MODEL: dodo_aggregator_arbitrum_trades.sql
🟠 Modified by:
🔧 PR: #3398, Revert 'add DODOFeeProxy on op & arb & polygon (#3398)'
🧙 Author: @jeff-dude on 2023-05-26
📝 Summary: The removed code was filtering data from the DODORouteProxy table based on a time range and then combining it with data from the DODOFeeRouteProxy table. The added code simply replaces an array cast with an empty string in the trace_address column of the DODOV2Proxy02_evt_OrderHistory table.
🔧 PR: #3398, add DODOFeeProxy on op & arb & polygon
🧙 Author: @owen05 on 2023-05-26
📝 Summary: The SQL model has been updated to include a UNION ALL statement that combines data from two different sources, DODORouteProxy_evt_OrderHistory and DODOFeeRouteProxy_evt_OrderHistory. The new section includes additional columns such as block_time, project version, taker and maker addresses along with token amounts for both sold and bought tokens. Additionally, the trace_address column is now an empty array of big integers instead of an empty string. Finally, the blockchain column has been set to 'arbitrum'.
MODEL: dodo_aggregator_bnb_trades.sql
🟠 Modified by:
🔧 PR: #3398, Revert 'add DODOFeeProxy on op & arb & polygon (#3398)'
🧙 Author: @jeff-dude on 2023-05-26
📝 Summary: The diff shows changes made to three SQL models that query different tables in the Dodoex_bnb database. In each model, an array of big integers was replaced with an empty string for the trace_address column. The rest of the columns remain unchanged and include token_sold_address, project_contract_address, tx_hash and evt_index.
🔧 PR: #3398, add DODOFeeProxy on op & arb & polygon
🧙 Author: @owen05 on 2023-05-26
📝 Summary: The diff shows changes made to three SQL models that query different tables in the Dodoex_bnb database. In each model, a new column called 'trace_address' was added and its value set to an empty string in the original code but changed to an array of big integers using CAST function in the updated code. The other columns selected from their respective tables are token_sold_address, project_contract_address, tx_hash and evt_index.
MODEL: dodo_aggregator_ethereum_trades.sql
🟠 Modified by:
🔧 PR: #3398, Revert 'add DODOFeeProxy on op & arb & polygon (#3398)'
🧙 Author: @jeff-dude on 2023-05-26
📝 Summary: The diff shows changes made to a SQL model in a merged pull request. The changes involve replacing the CAST function with an empty string for trace_address column in multiple WITH statements that query different sources of DODO Ethereum data. The rest of the code remains unchanged, and each source is queried using its respective event OrderHistory table.
🔧 PR: #3398, add DODOFeeProxy on op & arb & polygon
🧙 Author: @owen05 on 2023-05-26
📝 Summary: The diff shows changes made to a SQL model in a merged pull request. The changes involve replacing an empty string with an array of big integers for the trace_address column in several WITH statements that query different sources from the DODO Ethereum database. The rest of each statement remains unchanged, selecting and renaming columns from their respective sources as token_sold_address, project_contract_address, tx_hash and evt_index.
MODEL: dodo_aggregator_optimism_trades.sql
🟠 Modified by:
🔧 PR: #3398, Revert 'add DODOFeeProxy on op & arb & polygon (#3398)'
🧙 Author: @jeff-dude on 2023-05-26
📝 Summary: The removed code was casting an empty array as a big integer array. The added code replaced the cast with an empty string for the trace_address column in a SQL model that queries two different sources of DODO order history data on Optimism blockchain. Additionally, there is now a conditional statement to filter results by date if it's incremental and only one source is being queried instead of two. Finally, the output specifies that this query pertains to Optimism blockchain only.
🔧 PR: #3398, add DODOFeeProxy on op & arb & polygon
🧙 Author: @owen05 on 2023-05-26
📝 Summary: The diff shows changes made to a SQL model. The original code selects data from one table, while the updated version adds another table using UNION ALL. The new table has different column names and some columns have NULL values or empty arrays assigned to them. There is also an optional filter for incremental updates based on block time in both tables. Finally, the output includes a constant string 'optimism' as blockchain identifier for all rows returned by this query.
MODEL: dodo_aggregator_polygon_trades.sql
🟠 Modified by:
🔧 PR: #3398, Revert 'add DODOFeeProxy on op & arb & polygon (#3398)'
🧙 Author: @jeff-dude on 2023-05-26
📝 Summary: The removed code was selecting data from DODOFeeRouteProxy_evt_OrderHistory table and unioning it with the existing query. The added code is filtering the results of DODORouteProxy_evt_OrderHistory based on a time range, using an empty string instead of an array for trace_address column, and adding a blockchain column to the final result set.
🔧 PR: #3398, add DODOFeeProxy on op & arb & polygon
🧙 Author: @owen05 on 2023-05-26
📝 Summary: The diff shows changes made to a SQL model. The original code selects data from the DODOV2Proxy02_evt_OrderHistory table, while the updated version adds another select statement that retrieves data from DODOFeeRouteProxy_evt_OrderHistory table using UNION ALL. Both select statements have similar column names and are filtered by evt_block_time if is_incremental() returns true. The output of this query includes blockchain information for Polygon network only ('polygon' AS blockchain). Additionally, an empty string in trace_address was replaced with CAST(ARRAY() as array).
SECTOR: timeswap
toggle to see all model updates
MODEL: timeswap_arbitrum_borrow.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze borrowing transactions on the TimeswapV2PeripheryUniswapV3BorrowGivenPrincipal_evt_BorrowGivenPrincipal and TimeswapV2PeripheryNoDexBorrowGivenPrincipal_evt_BorrowGivenPrincipal tables in the timeswap_arbitrum database. The view includes transaction details such as transaction hash, time, token type (token_0), maturity date, strike price, pool pair information (pool_pair), chain information (chain), token amount borrowed in both raw and USD-denominated values. It also joins with a prices table to convert token amounts into USD values based on current market rates.
MODEL: timeswap_arbitrum_lend.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query lending transactions on the TimeswapV2PeripheryUniswapV3 and TimeswapV2PeripheryNoDex contracts in Arbitrum. The view includes transaction hash, time, token type (token_0), transaction type (lend), maturity date, strike price, pool pair name and chain. It also calculates the token amount and USD value of each transaction based on current prices from an external source. The model supports incremental updates for recent data only.
MODEL: timeswap_arbitrum_pools.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a temporary table with data on various token pairs, including their symbols, addresses, decimals, strike prices and maturities. It also includes information on the pool pair and chain they belong to as well as borrow and lend contract addresses. This enables data analysts to perform analysis on these token pairs in order to gain insights into trading patterns or other relevant metrics.
MODEL: timeswap_ethereum_borrow.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query information about borrowing transactions in the TimeswapV2PeripheryUniswapV3BorrowGivenPrincipal_evt_BorrowGivenPrincipal table. The view includes transaction hash, time, token_0 flag, transaction type (borrow), maturity date and strike price of the option being borrowed against. It also includes pool pair and chain information for each borrow event as well as token amount and USD value at the time of borrowing. Analysts can filter by blockchain type (Ethereum) and timeframe (last week).
MODEL: timeswap_ethereum_lend.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query lending transactions on the TimeswapV2PeripheryUniswapV3LendGivenPrincipal_evt_LendGivenPrincipal table. The view includes transaction hash, time, token_0 flag, transaction type (always 'lend'), maturity date and strike price of the option being lent out. It also includes pool pair and chain information for each transaction as well as token amount and USD value at the time of the event. Analysts can filter by blockchain or date range if desired.
MODEL: timeswap_ethereum_pools.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a table with information about a specific pool pair, including the symbols and addresses of two tokens, their decimals, strike price, maturity date and contract addresses for borrowing and lending. This enables data analysts to easily access this information for analysis or use in other models.
MODEL: timeswap_polygon_borrow.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query and analyze borrowing transactions on the Polygon network's TimeswapV2PeripheryUniswapV3BorrowGivenPrincipal smart contract. The view includes transaction details such as time, token amount borrowed, USD value of the borrow, maturity date and strike price of the option being traded. It also joins with other tables to provide additional information about pool pairs and pricing data for tokens involved in each transaction. This allows analysts to gain insights into borrowing trends on Polygon's DeFi ecosystem over time.
MODEL: timeswap_polygon_lend.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a view that enables data analysts to query lending transactions on the Polygon network. The view includes transaction hash, time, token type (0 or 1), transaction type (lend), maturity date, strike price, pool pair and chain information for each transaction. Additionally, it calculates the token amount and USD value of each lend transaction based on current market prices obtained from an external source. The view is designed to be incremental over the past week's data if desired by users.
MODEL: timeswap_polygon_pools.sql
🟢 Added by:
🔧 PR: #3387, Add Spell for Timeswap Labs
🧙 Author: @RaveenaBhasin on 2023-05-26
📝 Summary: This SQL model creates a temporary table with data on various token pairs, including their symbols, addresses, decimals, strike prices and maturities. This enables data analysts to easily query and analyze information about these token pairs on the Polygon chain.
SECTOR: equalizer_exchange
toggle to see all model updates
MODEL: equalizer_exchange_fantom_trades.sql
🟠 Modified by:
🔧 PR: #3423, Set Equalizer's project_start_date
🧙 Author: @ftm1337 on 2023-05-26
📝 Summary: In this SQL model, the project start date variable was updated from November 23rd to November 3rd. The join with a source called 'prices' now includes an incremental condition that filters for data within the last week. No other changes were made in this diff of the model.
SECTOR: aave
toggle to see all model updates
MODEL: aave_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The SQL model is being modified by adding a left join to the
AaveGovernanceV2_evt_ProposalQueuedtable. Additionally, there is an if statement that checks whether the query is incremental and filters out any records withevt_block_timeearlier than the maximum created_at value in the current table.MODEL: aave_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The removed lines were filtering the query to only include data from the past week and excluding any blockchain that is not Ethereum. The added line re-includes Ethereum as a valid blockchain for this query.
SECTOR: compound
toggle to see all model updates
MODEL: compound_v2_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The SQL model is being modified by adding a left join to the table GovernorBravoDelegate_evt_ProposalQueued. The previous left join was on an incorrect id and has been corrected. There is also a conditional statement that checks if the model is incremental, and if so, filters out any rows where evt_block_time occurred before the maximum created_at value in this table.
MODEL: compound_v2_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The added code is a condition that filters the data to only include Ethereum blockchain data. The removed code includes an incremental update condition and a filter for events occurring after the maximum block time in the table. Two left joins are used to join tables on proposal ID and minute, respectively. A symbol 'COMP' is also specified as part of this join operation, with prices being calculated based on date truncation at minute intervals using evt_block_time as input parameter.
SECTOR: dydx
toggle to see all model updates
MODEL: dydx_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The added code includes a left join to the
DydxGovernor_evt_ProposalQueuedtable and an optional filter based on theevt_block_timecolumn. The removed code was just a commented out line that also included a left join to the same table.MODEL: dydx_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The removed lines were filtering the query to only include data from the past week and excluding any data that was already processed. The added line is joining a table called 'prices' on specific conditions related to time and currency symbol.
SECTOR: ens
toggle to see all model updates
MODEL: ens_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: In this SQL model, a left join is added to the ENSGovernor_evt_ProposalQueued table. The previous left join to that table was removed. There is also an if statement checking if the model is incremental and filtering based on block time in that case.
MODEL: ens_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The added code includes a left join to a table called 'prices' on the minute and symbol columns, with an additional condition that blockchain must be equal to 'ethereum'. The removed code included two conditions related to incremental updates: one for filtering by date range and another for filtering by block time.
SECTOR: gitcoin
toggle to see all model updates
MODEL: gitcoin_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: In this SQL model, a left join is added to the table 'GovernorAlpha_evt_ProposalQueued' and the condition for joining it is changed from pex.id = pcr.id to pqu.id = pcr.id. The previous WHERE clause that filtered rows based on evt_block_time was removed.
MODEL: gitcoin_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The removed lines were filtering the USD price data to only include prices from the past week and limiting the query to only events that occurred after a certain block time. The added line is simply specifying that we want blockchain data for Ethereum.
SECTOR: uniswap
toggle to see all model updates
MODEL: uniswap_v3_ethereum_proposals.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The diff shows that a LEFT JOIN was added to a CTE called cte_sum_votes on the proposalId column of pcr table. Three more LEFT JOINS were added to tables named GovernorBravoDelegate_evt_ProposalCanceled, GovernorBravoDelegate_evt_ProposalExecuted and GovernorBravoDelegate_evt_ProposalQueued respectively. An IF statement was removed which checked if the model is incremental and filtered data based on it.
MODEL: uniswap_v3_ethereum_votes.sql
🟠 Modified by:
🔧 PR: #3425, (Quick) Fix to DAOs models
🧙 Author: @augustog on 2023-05-26
📝 Summary: The added code is a left join to the 'prices' table on minute and symbol columns, with an additional condition that blockchain should be ethereum. The removed code includes a conditional statement for incremental updates and a WHERE clause filtering events based on their block time being greater than the maximum block time in the current model.
Beta Was this translation helpful? Give feedback.
All reactions