import { type PoolClient } from '@evershop/postgres-query-builder'; /** * Blog module — initial schema (spec: specifications/blog-module.md §4). * * Tables are created in FK-dependency order: blog_category + blog_tag first, * then blog_post (FK → blog_category), then the description / pivot / comment / * reaction tables. Indexes (§4.7) and the url_key triggers (§4.8) follow. * * NOTE on cross-module FKs: `blog_post.author_id` (→ auth.admin_user) and * `blog_comment.customer_id` (→ customer.customer) are kept as plain INT columns * WITHOUT a database foreign key — module migration order across modules is not * guaranteed, so a hard FK here could run before `admin_user`/`customer` exist. * The resolvers tolerate a missing/orphaned id (return null). Visibility on the * storefront is `status = 1` only (no scheduler — §4.6). */ declare const _default: (connection: PoolClient) => Promise; export default _default;