Files
veola/internal/db/schema.sql
prosolis feea126c5e Add per-user item ownership and isolation
Items are now private to their owner. Add items.user_id (migrated in
place, existing items backfilled to the first admin) and scope every
item, results, and dashboard view to the signed-in user via owner-scoped
queries plus an ownedItem 404 guard. Admins get strict isolation too;
elevation stays limited to settings and user management.

Alert routing follows ownership: deal emails go only to the item owner
and the weekly digest is built per-recipient from their own items. The
scheduler still polls every active item; the Apify/eBay budget stays a
shared pool visible to all.

Add TestItemsArePrivatePerUser and seed owners in db tests.
2026-06-20 13:39:19 -07:00

147 lines
5.6 KiB
SQL

PRAGMA journal_mode=WAL;
PRAGMA foreign_keys=ON;
CREATE TABLE IF NOT EXISTS users (
id INTEGER PRIMARY KEY AUTOINCREMENT,
username TEXT NOT NULL UNIQUE,
password_hash TEXT NOT NULL,
role TEXT NOT NULL DEFAULT 'user',
email TEXT,
-- auth_source records how the row was provisioned: 'local' (password
-- login / setup) or 'forward' (Traefik forward-auth from Authentik). For
-- forward rows the role is re-synced from the IdP group on every request.
auth_source TEXT NOT NULL DEFAULT 'local',
email_deal_alerts INTEGER NOT NULL DEFAULT 0,
email_weekly_digest INTEGER NOT NULL DEFAULT 0,
created_at DATETIME DEFAULT CURRENT_TIMESTAMP
);
-- The email column and its unique index are created in db.go AFTER the
-- addColumnIfMissing migrations, so existing databases (whose users table
-- predates the email column) gain the column before the index references it.
CREATE TABLE IF NOT EXISTS items (
id INTEGER PRIMARY KEY AUTOINCREMENT,
-- user_id is the owning user. Items are private to their owner; the
-- scheduler still polls every active item regardless of owner. On existing
-- databases the column is added by addColumnIfMissing in db.go (without a
-- REFERENCES clause) and backfilled to the first admin, so user deletion
-- removes owned items explicitly in Store.DeleteUser rather than relying on
-- the cascade below.
user_id INTEGER REFERENCES users(id) ON DELETE CASCADE,
name TEXT NOT NULL,
search_query TEXT,
url TEXT,
category TEXT,
target_price REAL,
ntfy_topic TEXT NOT NULL,
ntfy_priority TEXT DEFAULT 'default',
poll_interval_minutes INTEGER DEFAULT 60,
include_out_of_stock INTEGER DEFAULT 0,
min_price REAL,
exclude_keywords TEXT,
listing_type TEXT,
condition TEXT,
region TEXT,
actor_active TEXT,
actor_sold TEXT,
actor_price_compare TEXT,
use_price_comparison INTEGER DEFAULT 0,
active INTEGER DEFAULT 1,
last_polled_at DATETIME,
last_poll_error TEXT,
best_price REAL,
best_price_currency TEXT,
best_price_store TEXT,
best_price_url TEXT,
best_price_image_url TEXT,
best_price_title TEXT,
created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
);
CREATE INDEX IF NOT EXISTS idx_items_active ON items(active);
-- idx_items_user is created in db.go AFTER addColumnIfMissing adds user_id, so
-- it works on databases whose items table predates the column (this CREATE
-- INDEX would otherwise fail on them, since IF NOT EXISTS on the table is a
-- no-op and the old table lacks user_id).
CREATE TABLE IF NOT EXISTS item_marketplaces (
item_id INTEGER NOT NULL REFERENCES items(id) ON DELETE CASCADE,
position INTEGER NOT NULL,
marketplace TEXT NOT NULL,
PRIMARY KEY (item_id, position)
);
CREATE INDEX IF NOT EXISTS idx_item_marketplaces_item ON item_marketplaces(item_id);
CREATE TABLE IF NOT EXISTS results (
id INTEGER PRIMARY KEY AUTOINCREMENT,
item_id INTEGER NOT NULL REFERENCES items(id) ON DELETE CASCADE,
title TEXT,
price REAL,
currency TEXT NOT NULL,
url TEXT,
source TEXT,
image_url TEXT,
matched_query TEXT,
alerted INTEGER DEFAULT 0,
found_at DATETIME DEFAULT CURRENT_TIMESTAMP,
ends_at DATETIME
);
CREATE INDEX IF NOT EXISTS idx_results_item ON results(item_id, found_at DESC);
CREATE INDEX IF NOT EXISTS idx_results_dedup ON results(item_id, url);
CREATE TABLE IF NOT EXISTS price_history (
id INTEGER PRIMARY KEY AUTOINCREMENT,
item_id INTEGER NOT NULL REFERENCES items(id) ON DELETE CASCADE,
price REAL NOT NULL,
store TEXT,
polled_at DATETIME DEFAULT CURRENT_TIMESTAMP
);
CREATE INDEX IF NOT EXISTS idx_price_history_item ON price_history(item_id, polled_at DESC);
CREATE TABLE IF NOT EXISTS settings (
key TEXT PRIMARY KEY,
value TEXT,
updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
);
INSERT OR IGNORE INTO settings (key, value) VALUES
('apify_api_key', ''),
('ntfy_base_url', ''),
('ntfy_default_topic', 'veola'),
('global_poll_interval_minutes', '60'),
('match_confidence_threshold', '0.6'),
('apify_cost_per_call', '0.00'),
('monthly_budget_usd', '0.00'),
('resend_api_key', ''),
('resend_from', '');
-- apify_api_usage tracks Apify actor runs per UTC day so the operator (and
-- every signed-in user) can see consumption and an estimated spend. Apify
-- bills per actor run / per result, which Veola cannot read back exactly, so
-- this is a call counter multiplied by a configurable per-call cost estimate.
CREATE TABLE IF NOT EXISTS apify_api_usage (
usage_date TEXT PRIMARY KEY,
call_count INTEGER NOT NULL DEFAULT 0
);
-- ebay_api_usage tracks Browse API calls per day so Veola can surface
-- consumption and halt polling before the developer keyset's daily call
-- limit is exceeded. usage_date is YYYY-MM-DD in US Pacific time, matching
-- eBay's own quota reset.
CREATE TABLE IF NOT EXISTS ebay_api_usage (
usage_date TEXT PRIMARY KEY,
call_count INTEGER NOT NULL DEFAULT 0
);
CREATE TABLE IF NOT EXISTS sessions (
token TEXT PRIMARY KEY,
data BLOB NOT NULL,
expiry REAL NOT NULL
);
CREATE INDEX IF NOT EXISTS idx_sessions_expiry ON sessions(expiry);