SELECT id, user_id, service, username, name, email, person_id, last_login_at FROM acts_external_users WHERE person_id IS NOT NULL; isn't particularly revealing...
Users can exist in ExternalUser with null user_id but I think that is a bug. If I go to my externaluser and set user_id = NULL it gets automatically fixed on my next login back to user_id = 4093. On the other hand if I also change my email address (so the software can't automatically fix the null user_id) it acts as though my externaluser doesn't exist and asks me to set up a new account.
I think we should go through the externaluser table and fix all the null user_id's that would be fixed if they logged in (should be an SQL one-liner) then delete the rest, set acts_external_user.user_id to non-nullable, and delete acts_external_user.person_id.
innodb_ft_user_stopword_table) from the relevant indices? I don't think we need a stopword list for our application as we aren't indexing whole paragraphs of text and users aren't searching for questions.
insert into statement at the mysql console…
RE: support ticket #2731
I changed the name on that person's main public profile and merged their other (smaller) public profile into this however it still shows up in the search results (despite running sudo -u www-data /usr/local/bin/camdram-console camdram). Additionally their old URL is now dead rather than redirecting -- are these bugs or did I just expect camdram to do something that it's never done in the past :P
master :tada: