-
|
Hey there! I'm experimenting with the psql indexer as we already have postgres in our stack. Unfortunately though we already have a table named Is there a way to change these or make them configurable to the developer outside o 8000 f a fork? They appear to be constants in the codebase. Modifying the initial migration is trivial after that too. I'm using Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
|
Hey, thank you for reporting. I see that this is a feature/problem, feel free to open an issue (or convert this discussion into one). We don't have per-database configuration flags in our systems for doing so. The file you pointed out, for instance, does not receive any configuration instance from which we could customize fields... |
Beta Was this translation helpful? Give feedback.
-
|
@alecsavvy did you take a look at the data companion? Does that address your use case? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
hey @sergio-mena, I'll take a look at that! The recently merged PR gets us where we need because we were already trying to use the psql indexer. Data companion looks like the right way to move off of psql in the future. Are there dates or plans for the psql deprecation yet? Would that also affect RPC clients like the |
Beta Was this translation helpful? Give feedback.
-
|
@alecsavvy no official date yet, but it will eventually happen when we see projects are using the data companion without issues. It will affect anything in CometBFT that needs indexing to happen in-process; so |
Beta Was this translation helpful? Give feedback.
-
|
Hey @sergio-mena, in regards to the implementation of the data companion, I see that here it uses an exposed RPC endpoint. We're considering using the |
Beta Was this translation helpful? Give feedback.
#3594