db-convex

To define a Convex schema, use defineTable with typed fields, then chain index and searchIndex methods for efficient querying. This ensures consistent data access patterns and proper runtime configurations across your TypeScript schema definitions.

Structure Convex queries, mutations, and actions by using clear function type patterns for each: query for reactive data fetching, mutation for state changes, and action or httpAction for server-side logic. Consistent patterns reduce boilerplate and prevent common pitfalls.

Use Convex mutations for synchronous database state changes and actions for asynchronous operations requiring external API calls or multi-step logic. Actions run in a separate runtime environment and cannot directly read or write the database without calling internal queries or mutations.

Avoid common Convex anti-patterns by following CLAUDE.md guidelines: always define indexes on frequently queried fields, use searchIndex for text search, enforce proper runtime configurations, and apply consistent defineTable patterns across all server functions.

Yes, Convex workflows let you orchestrate multiple server actions and mutations in a structured sequence. This helps manage complex operations by chaining actions together with consistent patterns and proper runtime configurations across your TypeScript project.

Convex queries without indexes scan entire tables, causing slow performance. Define indexes on frequently filtered fields using the index method in defineTable to optimize reactive query execution and ensure efficient data retrieval across your schema.