Skip to main content

16 docs tagged with "database"

View all tags

Database Schema — ChurchWiseAI Web

All tables owned or primarily used by churchwiseai-web — voice agent, chatbot, subscriptions, care, ShareWiseAI, SermonWise, and operational tables

Database Schema Reference

Index of all Supabase table documentation — shared production database used by all three active codebases. See sub-docs for per-codebase schema detail.

Multi-vertical tenant schema — design spec

Exact DDL, column-level changes, migration sequence, and code-path updates for the shared-core + per-vertical-tenant-tables architecture chosen on 2026-04-21. This is the implementation companion to the decision doc.

product_knowledge WARNING audit — 2026-05-11

Documents the 158 remaining WARNINGs in validate_product_knowledge() as batch-provisioning artifacts, not real data quality issues. Includes the 3 content corrections applied during this audit.

Query Product Analytics for Reporting

Supabase SQL queries for product metrics — chatbot conversation counts, voice call volume, ITW page views, premium church counts, and cross-property revenue summary

Regenerate Vector Embeddings

Regenerate OpenAI text-embedding-3-small vectors for unified_rag_content rows — identify rows with null embeddings, run the embedding script, and verify RAG search improves

Run a Database Schema Migration

Apply a schema change to the shared production Supabase database — write migration SQL, verify with dry run, get founder approval for destructive ops, execute, and save to pewsearch/migrations/

Supabase Integration

Single shared Supabase PostgreSQL instance (dev + prod) — client setup, auth configuration, RLS policies, storage buckets, and safety rules for the shared production database

Technical Operations Runbooks

Index of technical ops runbooks — DB migrations, performance, embedding regeneration, error triage, security incidents, Stripe webhook debugging, view refresh, cost audit, backup verification, and running tests

Verify Data Backups Are Intact

Confirm Supabase automated backups are running — verify backup timestamps, run record count checks on critical tables (unified_rag_content, churches, premium_churches)