← Graph

Geneva Drive hero constraints and migrations

question 2 connections

Audience asks whether heroes have special requirements and whether Julik provides generators for hero migrations. Julik: the hero is just an Active Record — no constraints beyond a DB uniqueness constraint on (hero_type, hero_id, workflow_type) used to enforce 'only one billing workflow per user'. Geneva Drive ships an install generator that creates its own migrations and adapts to big-int vs UUID primary keys; no changes are needed on the application's other tables.

answer_summary
Heroes are plain Active Records with a (hero_type, hero_id, workflow_type) uniqueness constraint; Geneva Drive's install generator creates all its own migrations and adapts to BIGINT/UUID pk formats.
question Geneva Drive hero constraints and migrations
about
Geneva Drive project
Covers install generator and uniqueness constraint.
question Geneva Drive hero constraints and migrations
asked_at
Audience question on hero requirements and migration tooling.

Provenance