We need to ensure that Indexer V2 is backward compatible and works with the transactions in our current database. - Compare Indexer V2’s schema (as defined in the code or via migrations) against our current schema (used by the current Movement indexer DB) - Identify any: - Removed fields - Renamed tables - Changed types - Additional data not present in current DB
We need to ensure that Indexer V2 is backward compatible and works with the transactions in our current database.
Compare Indexer V2’s schema (as defined in the code or via migrations) against our current schema (used by the current Movement indexer DB)
Identify any: