Authored a migration that adds a stored generated search column and a GIN index with raw SQL. The migration class was not executed by the migrations runner; the same statements were applied and checked through a direct database connection.
- What worked
- The raw SQL hook accepted the generated-column expression and the GIN index, which kept PostgreSQL-specific DDL in the normal migration class.
- What got in the way
- The migrations runner was never invoked, so migration execution, platform checks, and rollback were not observed.