import "server-only";

import { count, eq } from "drizzle-orm";
import { CameraWeb, db, Rooms, User } from "@/lib/db";

/**
 * Row counters for the public homepage.
 *
 * These live in one place on purpose: the homepage and the boot warm-up both
 * populate the same cache keys, so two different implementations would race to
 * write different values into the same entry.
 */

/*
 * These are exact counts on purpose.
 *
 * `information_schema.TABLES.TABLE_ROWS` was tried here as a cheap stand-in,
 * because an exact COUNT(*) walks an index. Measured against the real database
 * it turned out to be pointless: `users` has 165 rows, `rooms` 92 and
 * `camera_web` 0, and the estimate was 0.00% off on all three. An index scan
 * over 165 rows costs less than the round trip the estimate would have saved,
 * while the estimate carries a real risk of displaying a plausible but wrong
 * member count — and InnoDB's accuracy degrades as a table grows. If these
 * tables ever reach six figures, revisit the trade; below that, exactness is
 * free.
 */

export async function countUsers(): Promise<number> {
	const [row] = await db.select({ total: count() }).from(User);
	return row?.total ?? 0;
}

export async function countRooms(): Promise<number> {
	const [row] = await db.select({ total: count() }).from(Rooms);
	return row?.total ?? 0;
}

export async function countPhotos(): Promise<number> {
	const [row] = await db.select({ total: count() }).from(CameraWeb);
	return row?.total ?? 0;
}

/**
 * Online users is deliberately *not* estimated: it is read from an index over a
 * small subset of rows, it is the one counter people watch closely, and being a
 * few seconds behind looks broken rather than approximate.
 */
export async function countOnline(): Promise<number> {
	const [row] = await db
		.select({ total: count() })
		.from(User)
		.where(eq(User.online, "1"));
	return row?.total ?? 0;
}