dbastrikin 288bb1c375 fix: compute expires_at in SQL instead of generated column ...

TIMESTAMPTZ + INTERVAL is STABLE (depends on timezone), not IMMUTABLE,
so PostgreSQL rejects it in GENERATED ALWAYS AS STORED columns.
Fix: remove generated column and compute expires_at inline in each query
as (added_at + storage_days * INTERVAL '1 day').

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-02-21 23:24:42 +02:00

..

001_create_users.sql

feat: implement Iteration 0 foundation (backend + Flutter client)

2026-02-20 13:14:58 +02:00

002_create_ingredient_mappings.sql

feat: implement Iteration 1 — AI recipe recommendations

2026-02-21 22:43:29 +02:00

003_create_recipes.sql

feat: implement Iteration 1 — AI recipe recommendations

2026-02-21 22:43:29 +02:00

004_create_saved_recipes.sql

feat: implement Iteration 1 — AI recipe recommendations

2026-02-21 22:43:29 +02:00

005_add_ingredient_search_indexes.sql

feat: implement Iteration 2 — product management

2026-02-21 23:22:30 +02:00

006_create_products.sql

fix: compute expires_at in SQL instead of generated column

2026-02-21 23:24:42 +02:00