payload-drizzle

To perform bulk PayloadCMS database updates without hooks, use the local API for standard operations and direct Drizzle access via payload.db.drizzle for high-volume data migrations, bypassing the full request lifecycle for performance.

The best way to run complex SQL queries against a PayloadCMS database is combining the local API for standard operations with direct Drizzle access, leveraging generated Drizzle schemas for strong typing and bypassing the request lifecycle for performance-critical tasks.

Yes, you need a generated Drizzle schema to access the PayloadCMS database directly, as it provides the type-safety and tooling required to manage hasMany join tables explicitly and execute high-volume operations safely.

When bypassing the PayloadCMS local API for bulk operations, you must explicitly manage hasMany join tables using direct Drizzle queries, ensuring proper data relationships are maintained without relying on the standard request lifecycle.

Direct Drizzle access should be used for high-volume database operations, complex SQL queries, and performance-critical imports where bypassing Payload's full lifecycle, hooks, and access checks provides a necessary speed advantage over the local API.

Yes, you can combine them in a dual-API workflow by using the safe local Payload API for standard operations and direct Drizzle access for bulk data migrations or complex queries, preserving safety defaults while optimizing performance.