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
Copy file name to clipboardexpand all lines: docs/reindexing.md
+8-2
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,15 @@ When deploying changes to the indexer, it's important to clarify the results you
12
12
- The indexer will create a new schema in Postgres named `chain_data_${version}`. If this schema does not exist, it will be created, all necessary tables will be set up, and indexing will start from scratch.
13
13
- If the schema already exists, the indexer will resume indexing from the last indexed block unless the `--drop-db` flag is specified via the CLI. This will drop the existing database and start fresh.
14
14
15
-
### Using `--drop-db` in Development
15
+
### Dropping Schemas in Development
16
16
17
-
- During development, you can use the `--drop-db` flag to ensure the indexer always deletes the existing schema and migrates from scratch. This can be useful for testing schema changes and event handler modifications without retaining old data.
17
+
- During development, you can use the `--drop-db` flag to ensure the indexer always deletes all existing schema and migrates from scratch. This can be useful for testing schema changes and event handler modifications without retaining old data.
18
+
19
+
- During development, you can use the `--drop-chain-db` flag to ensure the indexer always deletes chain schema and migrates from scratch.
20
+
21
+
- During development, you can use the `--drop-ipfs-db` flag to ensure the indexer always deletes ipfs schema and migrates from scratch.
22
+
23
+
- During development, you can use the `--drop-price-db` flag to ensure the indexer always deletes price schema and migrates from scratch.
0 commit comments