-- 037_requisition_period_jd_entity.sql
-- Annexure A revision 2 added three fields the original 020 table never had:
-- "If not permanent, specify the period From/To" on the position block, the
-- mandatory "JD Available Yes/No" flag (distinct from the free-text
-- job_description), and "Entity" alongside Employee Name/Department in the
-- internal-recommendation block. Matches Requisition in
-- backend/candidate_forms/models.py. Applied at startup by
-- alembic_setup.run_manual_sql() — needed because prod boots with
-- DB_AUTOGENERATE=false and never autogenerates new columns.

ALTER TABLE app.requisitions
    ADD COLUMN IF NOT EXISTS period_from date,
    ADD COLUMN IF NOT EXISTS period_to date,
    ADD COLUMN IF NOT EXISTS jd_available boolean,
    ADD COLUMN IF NOT EXISTS entity varchar;