@derivedFrom on Non-List Field: The Graph and SubQuery Guidance
Resolve @derivedFrom non-list field modeling questions with practical schema patterns for SubQuery and GraphQL-based indexing.
This guide addresses common @derivedFrom modeling questions raised by developers migrating or comparing GraphQL indexing patterns.
Schema modeling recommendation
Prefer explicit relation entities when cardinality is ambiguous. This avoids one-to-one assumptions that break under event ordering and historical backfills.
Migration safety
Run schema validation tests and replay a deterministic block window before production deploy to ensure relation fields resolve consistently.
