The schema drop script leaves 115 functions behind
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Running projects/ores.sql/drop/drop.sql against a full database removes
every ores_ table and view but leaves 115 ores_ functions: refdata 63, iam
14, dq 11, synthetic 10, utility 7, and a few elsewhere. Examples are the
refdata publish-from-DQ functions, ores_refdata_parties_hierarchy_fn and
ores_dq_badge_severities_upsert_fn. Many drop files print "function … does
not exist, skipping" during the same run, which suggests drop files that name a
different signature than the function they target.
2. Why
A drop that leaves objects behind hides itself: a later create replaces the functions, so nothing fails. It matters for any teardown that does not drop the whole database, and it means the drop tree does not match the create tree.
3. References
- Measured on
bright_faradaywhile wiring the five missing drop files in Find why so much SQL is hand-written and generate what codegen can.