fix: split token count columns into separate migration
A previous commit added prompt_eval_count and eval_count to the existing 2026-05-27-000002_add_insight_generation_params migration, but Diesel won't re-run an already-applied migration. Environments that applied the original version of 000002 never got these two columns, causing "no such column: photo_insights.prompt_eval_count" on every insight read. - Revert 000002 up.sql to its original 7-column form - Add 000003_add_insight_token_counts for the two missing columns Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
-- Persist generation parameters and token usage on each insight row.
|
||||
-- Persist generation parameters on each insight row for auditing.
|
||||
ALTER TABLE photo_insights ADD COLUMN num_ctx INTEGER;
|
||||
ALTER TABLE photo_insights ADD COLUMN temperature REAL;
|
||||
ALTER TABLE photo_insights ADD COLUMN top_p REAL;
|
||||
@@ -6,5 +6,3 @@ ALTER TABLE photo_insights ADD COLUMN top_k INTEGER;
|
||||
ALTER TABLE photo_insights ADD COLUMN min_p REAL;
|
||||
ALTER TABLE photo_insights ADD COLUMN system_prompt TEXT;
|
||||
ALTER TABLE photo_insights ADD COLUMN persona_id TEXT;
|
||||
ALTER TABLE photo_insights ADD COLUMN prompt_eval_count INTEGER;
|
||||
ALTER TABLE photo_insights ADD COLUMN eval_count INTEGER;
|
||||
|
||||
Reference in New Issue
Block a user