Chain based table name and default columns configuration

[iuwqyir]

TL;DR

Replaced custom BlockTimestamp type with standard time.Time and added chain-specific table configuration support.

What changed?

• Removed custom BlockTimestamp type and replaced all usages with standard time.Time
• Added TableConfig and TableOverrideConfig types to support chain-specific configurations
• Added ChainBasedConfig to ClickhouseConfig for per-chain table customization
• Introduced default field lists for blocks, transactions, logs, and traces
• Added methods to handle chain-specific table names and field selections
• Updated query execution to use chain-specific table names when configured

How to test?

1. Verify existing timestamps are correctly handled with time.Time
2. Configure chain-specific table overrides in config:

chainConfig:
  "1":
    blocks:
      tableName: "eth_blocks"
      defaultSelectFields: ["chain_id", "block_number", "hash"]

3. Verify queries use correct table names and fields for specified chains
4. Confirm default behavior remains unchanged for chains without specific configurations

Why make this change?

• Simplifies timestamp handling by using standard Go time.Time type
• Enables chain-specific table configurations for more flexible deployments, especially during migrations
• Allows customization of field selection and table names per chain
• Improves query optimization by allowing selective field retrieval

[iuwqyir]

• create an endpoint to query token balances #136
• Handle sigterm #150
• Chain based table name and default columns configuration #151 👈 (View in Graphite)
• Use VersionedCollapsingMergeTree and insert based deletes #149
• Specific column selection and api serialization #148
• Conform getTraces to api standard #147
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.