You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If you observe the error message 500: Database error querying schema in your Auth logs, it typically indicates that the Supabase Auth server has encountered NULL values in the auth.users table where a valid string or empty string is expected.
Why Does This Happen?
This issue usually occurs following manual SQL inserts or updates to the auth.users table. The Auth service expects specific columns to contain data or an empty string; when it encounters a NULL value instead, it triggers a validation error.
How to Resolve This:
Identify the column containing the NULL values (such as email) and execute the following command in the SQL Editor to convert them to empty strings:
UPDATEauth.usersSET<column_name>=''WHERE<column_name> IS NULL;
Replace <column_name> with the specific column causing the error. To prevent this from recurring, ensure that any future manual modifications to the auth schema adhere to the service's requirements.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If you observe the error message
500: Database error querying schemain your Auth logs, it typically indicates that the Supabase Auth server has encounteredNULLvalues in theauth.userstable where a valid string or empty string is expected.Why Does This Happen?
This issue usually occurs following manual SQL inserts or updates to the
auth.userstable. The Auth service expects specific columns to contain data or an empty string; when it encounters aNULLvalue instead, it triggers a validation error.How to Resolve This:
Identify the column containing the
NULLvalues (such asemail) and execute the following command in the SQL Editor to convert them to empty strings:Replace
<column_name>with the specific column causing the error. To prevent this from recurring, ensure that any future manual modifications to theauthschema adhere to the service's requirements.All reactions