this post was submitted on 03 Jun 2023
1 points (100.0% liked)
Lemmy Support
4645 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ok, figured it out myself. For anyone else that needs it..
Run a shell within the postgres docker container:
docker exec -it _postgres_1 sh
Connect to the postgres service:
psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy
Connect to the lemmy database:
\c lemmy
Then the user table: \d local_user
Find the user ID of the account you want to manually toggle, probably #1:
SELECT * from local_user;
Then update the email_verified and _accepted_application flag on the first account:
UPDATE local_user SET email_verified = 't', accepted_application = 't' WHERE id = 1;
lemmy=# UPDATE local_user SET email_verified = 't', accepted_application = 't' WHERE id = 3; UPDATE 1 lemmy=# UPDATE local_user SET email_verified = 't', email_verified= 't' WHERE id = 3; UPDATE 1 lemmy=#
Thanks for this breakdown, I seem to be having issues with the update statements:
lemmy=# UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 1; ERROR: column "‘t’" does not exist LINE 1: UPDATE local_user SET email_verified = ‘t’, accepted_applica... ^ HINT: Perhaps you meant to reference the column "local_user.id". lemmy=# UPDATE local_user SET email_verified =‘t’, accepted_application = ‘t’ WHERE id = 1; ERROR: column "‘t’" does not exist LINE 1: UPDATE local_user SET email_verified =‘t’, accepted_applicat... ^ HINT: Perhaps you meant to reference the column "local_user.id". lemmy=# UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 3; UPDATE 1 ERROR: column "‘t’" does not exist LINE 1: UPDATE local_user SET email_verified = ‘t’, accepted_applica... ^ HINT: Perhaps you meant to reference the column "local_user.id". lemmy-#
It seems that the query that Lodion shared has the wrong single quote character,
‘
rather than'
. Try using it with the latter, I had the same issue as you and this was what fixed it.yes, I should have realized that. That worked! Thank you @[email protected]
Now it worked, thanks!