mAi
755a1042ff
Phase 3 Slice 2 Step B-1 (design §3.B). UPDATE paliad.deadline_rules
to set is_court_set=true where the live isCourtDeterminedRule()
heuristic returns true:
primary_party = 'court'
OR event_type IN ('hearing', 'decision', 'order')
Expected delta on the production corpus: 47 rows flipped false→true
(every primary_party='court' rule overlaps with a court event_type
in the current data, so the two predicates fully overlap at 47).
Replicates the live fristenrechner.go body EXACTLY, not the
ILIKE-padded sketch in msg 1746. Per head's ruling msg 1750:
padding with '%entscheidung%' / '%urteil%' would mis-flag party
filings like RoP.151 (Antrag auf Kostenentscheidung) and § 83 PatG
(Stellungnahme zum Hinweisbeschluss) as court-set. They aren't —
only their anchors are.
Audit footnote: ~8 'Zustellung…' rules (LG-Urteil, OLG-Urteil,
BPatG-Entscheidung, Beschwerdeentscheidung, DPMA-Entscheidung)
carry primary_party='both' + event_type='filing'. Semantically the
Zustellung date IS court-set; flagging them is left to the legal-
review pass mentioned in design §2.3, not this slice.
Idempotent via WHERE is_court_set = false. Audit-reason is set via
set_config('paliad.audit_reason', …, true) so the mig 079 trigger
captures one paliad.deadline_rule_audit row per flipped rule —
the persistent backfill trail.
Mig 081 was reserved for proceeding_types display_order verification
in design §3.1; it was a no-op and was not authored. Tracker
skips 081, advances 80 → 82. golang-migrate handles non-contiguous
numbers fine as long as the order ascends.
22 lines
813 B
SQL
22 lines
813 B
SQL
-- t-paliad-183 down — reverts the is_court_set flips written by
|
|
-- 082_backfill_is_court_set.up.sql.
|
|
--
|
|
-- "Revert" here means: restore the post-Slice-1 default (false on every
|
|
-- row). We don't know after the fact which rows were already true
|
|
-- before the backfill (mig 078 created the column with DEFAULT false on
|
|
-- every existing row, so post-Slice-1 every row was false — there is
|
|
-- no pre-existing true population to preserve). Setting back to false
|
|
-- is therefore equivalent to "undo the backfill".
|
|
--
|
|
-- Audit-reason set so the trigger doesn't raise on the down-side
|
|
-- UPDATEs either.
|
|
|
|
SELECT set_config(
|
|
'paliad.audit_reason',
|
|
'rollback 082: reset is_court_set to mig 078 default (false)',
|
|
true);
|
|
|
|
UPDATE paliad.deadline_rules
|
|
SET is_court_set = false
|
|
WHERE is_court_set = true;
|