All Errors

PostgreSQL raises error 22013 when a window function frame specification uses an invalid value for PRECEDING or FOLLOWING row offsets. The frame size must be a non-negative integer expression, evaluated at runtime, and cannot be negative or NULL. This error occurs during query execution when the computed offset violates these constraints.

PostgreSQL prevents you from directly changing a column's data type if that column is used in a view or rule dependency. You must drop the dependent view(s) first, alter the column, and then recreate them in a transaction.

This Mongoose validation error occurs when attempting to save a document without providing a required email field. The error indicates that your schema defines email as required, but the field is missing or undefined in the data being saved.

This security exception occurs when a user attempts to search an index without the required read privileges in their assigned role. The error indicates missing RBAC permissions for the search operation.

MongoDB throws "BadValue: invalid parameter" during global initialization when it cannot parse the requested locale (LANG / LC_*). Setting a generated UTF-8 locale before mongod/mongos starts and ensuring services inherit those values keeps the server from failing with error code 2.

This ESLint error occurs when the @typescript-eslint/explicit-function-return-type rule is enabled and you define a function expression without explicitly annotating its return type. While TypeScript can infer return types, this linting rule enforces explicit annotations for better code clarity and type safety.

PostgreSQL raises this error when a regular expression pattern exceeds internal complexity limits in the POSIX regex engine. This typically occurs with deeply nested patterns, excessive alternations, or very long character classes. Simplify the regex pattern or break it into multiple smaller queries to resolve this issue.

This error occurs when attempting to update protected user fields for SSO-managed accounts in Supabase. Users authenticated via SAML SSO have immutable email and phone fields controlled by their identity provider.

This error occurs when you attempt to create a foreign key constraint that references a column without a PRIMARY KEY or UNIQUE constraint, or when there is a mismatch in column count or data types between the referencing and referenced columns.

This error occurs when trying to insert or update a document that violates the collection's validation rules. MongoDB rejects the operation to maintain data integrity based on the schema constraints you've defined.

This error occurs in AWS RDS when attempting to modify parameters in a default parameter group, which is immutable. AWS restricts changes to default groups for safety. Create a custom parameter group instead and apply it to your RDS instance to resolve this issue.

This error occurs when a Prisma Accelerate query exceeds the configured timeout limit. Common causes include slow queries, insufficient database connections during high traffic, or database resource contention.

The PostgreSQL error 42P09 (ambiguous_alias) occurs when a column reference in your query cannot be uniquely resolved because the same column name exists in multiple tables or aliases. This typically happens in JOIN operations, subqueries, or PL/pgSQL functions where the database cannot determine which table or alias the column belongs to.

Firebase Analytics limits projects to 25 unique user properties. When you attempt to set a 26th property, Analytics returns Code 9 and silently drops the new property without logging it.

PostgreSQL cannot acquire a necessary lock on a table because another transaction holds a conflicting lock. This error (code 55P03) typically occurs during DDL operations or when lock_timeout is exceeded.

This error occurs when a MongoDB aggregation pipeline stage exceeds the default 100MB memory limit and disk usage is not enabled. Enable allowDiskUse to resolve it.

PostgreSQL error 53000 occurs when the server cannot allocate necessary memory, disk space, or connection slots. This typically happens during large queries, bulk operations, or when system resources are exhausted, and requires adjusting configuration parameters or freeing up resources.

This MySQL client error occurs when data being sent or received doesn't fit the target column's type or size constraints. It commonly appears during INSERT/UPDATE operations or when fetching prepared statement results.

PostgreSQL error 42804 occurs when you attempt to insert, update, or assign a value of one data type to a column with an incompatible data type. This strict type checking requires explicit casting to resolve mismatches between the target column type and the value being assigned.

This error occurs when there's a network or routing issue between your client and Supabase's edge gateway. The relay layer handles authentication, routing, and traffic management for Edge Functions.