All Errors

This error occurs when MySQL cannot write temporary files to disk, usually due to insufficient permissions on the tmpdir, a full filesystem, or file descriptor limits being reached.

This error occurs when an INSERT or UPDATE operation violates a database constraint (UNIQUE, NOT NULL, PRIMARY KEY, FOREIGN KEY, or CHECK). SQLite aborts the statement and rolls back its changes while preserving earlier transaction operations.

This error occurs when attempting to create a MySQL resource group with a name that already exists in the database. The fix involves either dropping the existing group, using a different name, or altering the existing group instead.

SQLITE_CANTOPEN occurs when SQLite cannot access the database file due to missing files, incorrect paths, or permission issues. This guide covers checking file permissions, using absolute paths, and ensuring directory access.

This error occurs when an index mapping requires a routing value for all CRUD operations, but the request does not provide one. The routing parameter determines which shard stores a document.

This error occurs when attempting write operations (SET, DEL, etc.) inside a Lua script executed with EVAL_RO or by a read-only user. Use EVAL for write operations or ensure your script only performs reads.

PostgreSQL error 2F002 occurs when attempting to execute data-modifying statements (INSERT, UPDATE, DELETE) within a function or routine that is declared as read-only or has volatility restrictions preventing database modifications.

This timeout exception occurs when Elasticsearch nodes fail to receive responses within the expected timeout period during inter-node communication, typically caused by network latency, high cluster load, or resource constraints.

This error occurs when custom claim attributes passed to setCustomUserClaims() contain invalid data types or exceed size limits. Fix it by ensuring claims are JSON-serializable and under 1000 bytes.

This error occurs when a Supabase auth hook exceeds its execution time limit - 2 seconds for Postgres hooks or 5 seconds for HTTP hooks. The authentication flow is interrupted to prevent delays.

This error occurs when a Prisma Pulse subscription is terminated unexpectedly, often due to connection issues, resource limits, or manual cancellation. Understanding subscription lifecycle management is key to preventing this error.

This error occurs when Supabase detects a refresh token being reused outside the allowed reuse interval, typically due to race conditions in SSR applications or network issues causing stale tokens to be retried.

This error occurs when Prisma Client tries to query a table that hasn't been created in your database yet. It typically happens when your schema.prisma file is out of sync with your actual database schema.

This error occurs when Prisma attempts to use transactions on a standalone MongoDB instance. MongoDB requires replica sets for transaction support, which Prisma uses internally for nested writes and data consistency.

This error occurs when a Lua script in Redis Cluster accesses keys without explicitly declaring them in the KEYS array. Redis Cluster requires all key names to be passed as input arguments for proper shard routing.

This error occurs when attempting to mark a migration as rolled back using `prisma migrate resolve --rolled-back`, but the migration is not currently in a failed state. The rollback flag only works with migrations that have actually failed during application.

This MongoDB error occurs when a query or aggregation pipeline attempts to compare a field value to undefined, which is not a valid comparison type. MongoDB cannot directly compare values to undefined because it treats undefined differently from null and missing fields.

This error occurs when a prepared SQL statement is no longer valid because the database schema was modified after the statement was prepared. SQLite detects the schema mismatch and refuses to execute potentially incorrect virtual machine code.

This error occurs when Prisma Migrate cannot automatically create a temporary shadow database during development migrations. The shadow database is used to detect schema drift and validate migrations before applying them.

This HTTP 429 error occurs when you exceed Firebase's API rate limits while deploying Cloud Functions, typically when deploying many functions simultaneously or in rapid succession through CI/CD pipelines.