Publications

import { query } from "./_generated/server";
import { v } from "bijection/values";

// Both tables always come from the same publication.
export const customerSummary = query({
  args: { customer: v.string() },
  handler: async (ctx, args) => {
    const orders = await ctx.db
      .query("open_orders")
      .withIndex("by_customer", (q) => q.eq("customer", args.customer))
      .take(100);
    const totals = await ctx.db
      .query("customer_totals")
      .withIndex("by_customer", (q) => q.eq("customer", args.customer))
      .unique();
    return { orders, totals };
  },
});

​

How it fits together

• Published tables, declared in your schema with definePublished. Their rows are written only by publication; no mutation can insert, patch, replace or delete them.
• A pipeline, declared with defineEtl from the @bijection/pipelines component, which you install from npm and add to your app with app.use. It names the input tables, the output tables and the transform function that turns one into the other.
• A publisher, declared with definePublisher. It names the internal queries Bijection reads to find a ready result and verify it. defineEtl generates these queries and the declaration for you.

​

What publication guarantees

​

Next steps