hub/tasks/architecture/storage/add-call-graph-edges-indexes-cascades.md at 85ff26ae51e1045207da9ef7ae4fc8f963e2a913

alkdev/hub

Files

glm-5.1 2b63cda1c7 Setup repo: migrate architecture specs, code stubs, and tasks from alkhub_ts

Copy architecture docs, ADRs, storage domain specs, research, reviews,
and 56 storage architecture tasks from the alkhub_ts monorepo. Adapt for
standalone @alkdev/hub repo structure (src/ not packages/hub/).

Sanitize all sensitive information:
- Replace private IPs (10.0.0.1) with localhost defaults
- Remove internal server hostnames (dev1, ns528096)
- Replace /workspace/ private paths with npm package references
- Remove hardcoded credentials from examples
- Rewrite infrastructure.md without private network details

Add Deno project scaffolding: deno.json (pinned deps), .gitignore,
AGENTS.md, entry point. Migrate existing code stubs (crypto, config
types, logger) with updated import paths.

2026-05-25 10:56:32 +00:00

1.7 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

add-call-graph-edges-indexes-cascades

Add call_graph_edges indexes and cascade documentation

completed

narrow

medium

component

implementation

Description

call_graph_edges has no indexes and no cascade entries in table-reference.md. Both sourceId and targetId reference call_graph_nodes.id with CASCADE (from call-graph.md), but this is undocumented in the cross-cutting reference. Without indexes, graph traversal queries (find children, find parents) will require sequential scans.

Additionally, the relationship between call_graph_nodes.parentRequestId and call_graph_edges is ambiguous: do they store the same parent-child relationship redundantly, or serve different purposes?

Acceptance Criteria

table-reference.md index table includes: idx_call_graph_edges_source_id on (sourceId), idx_call_graph_edges_target_id on (targetId)
Consider and document whether unique constraint on (sourceId, targetId, edgeType) is needed to prevent duplicates
table-reference.md cascade table includes: call_graph_edges.sourceId → call_graph_nodes.id with CASCADE, call_graph_edges.targetId → call_graph_nodes.id with CASCADE
call-graph.md is updated with the index definitions
The parentRequestId vs call_graph_edges relationship is clarified in call-graph.md: document whether parentRequestId is a convenience shortcut or redundant with edges

References

docs/reviews/storage-architecture-review-2026-04-21.md#C10
docs/architecture/storage/call-graph.md:32-41
docs/architecture/storage/table-reference.md (missing entries)

Notes

To be filled by implementation agent

Summary

To be filled on completion

1.7 KiB Raw Blame History