Two populate scripts were never wired into a recreate

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

projects/ores.sql/populate/scheduler/scheduler_populate.sql seeds a job that scrapes MQ queue statistics every minute, and projects/ores.sql/populate/trading/trading_sample_data_populate.sql books a swap and a novation as demonstration data. No root script includes either one, so no database has ever run them. The scheduler file arrived with the move from pgmq to the scheduler (11168b35ba).

The trading file is settled: it booked wide trades, so it was deleted with the wide trade. The scheduler file is the one decision left.

2. Why

Each file is either a feature someone expected and does not have, or dead code. Wiring the scheduler job changes what runs on every database; wiring the sample trades adds them to every database. The wiring check now names both as deliberate exceptions until this is decided.

3. References

  • projects/ores.sql/utility/validation_ignore.txt, the WIRE_001 entries for both files.

4. See also

Emacs 29.3 (Org mode 9.6.15)