cameleer/cameleer-server
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

DIAG-02: Link transactions to active RouteGraph version at execution time #21

New Issue
Closed
opened 2026-03-11 11:13:56 +01:00 by claude · 2 comments
claude commented 2026-03-11 11:13:56 +01:00
Owner
Copy Link

Each transaction links to the RouteGraph version that was active at execution time, so users can see the exact route definition that was running when a transaction occurred.

Category: Route Diagrams
REQ-ID: DIAG-02

Each transaction links to the `RouteGraph` version that was active at execution time, so users can see the exact route definition that was running when a transaction occurred. **Category:** Route Diagrams **REQ-ID:** DIAG-02
claude commented 2026-03-11 21:21:57 +01:00
Author
Owner
Copy Link

Implemented in Phase 2. diagram_content_hash column added to route_executions table in ClickHouse. Populated during ingestion batch insert, linking each execution to its route diagram. Key files: 01-schema.sql, ClickHouseExecutionRepository.java.

Implemented in Phase 2. `diagram_content_hash` column added to `route_executions` table in ClickHouse. Populated during ingestion batch insert, linking each execution to its route diagram. Key files: `01-schema.sql`, `ClickHouseExecutionRepository.java`.
claude commented 2026-03-13 10:48:01 +01:00
Author
Owner
Copy Link

Implemented: diagram_content_hash column stored in route_executions table, linking transactions to the active RouteGraph version.

Implemented: `diagram_content_hash` column stored in `route_executions` table, linking transactions to the active RouteGraph version.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
Accessibility (a11y) improvements
 bug
Something isn't working correctly
 cleanup
Code cleanup, dead code removal, refactoring
 epic
Epic: groups related issues
 feature
New functionality
 pmf
Product-market fit: critical for first market offer
 route-diagram
Route diagram page and execution overlay
 security
Authentication, authorization, RBAC
 ui
Frontend / React UI
 ux
UX/usability improvements
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?