PHP errors "Duplicate entry 'UID' for key 'PRIMARY' query..."

i think that error may occur when a user account is created, but the fields which realname is set to use for realname creation have no content.

example:
realname uses a "last name" field to create the realname, but when the user account is created that field has no content

I have that issue myself, attached patch should fix it - check if the realname is an empty string, then use UPDATE instead of INSERT

when saving a user I have a similar problem but it's when the realname field in the database is set to '' for whatever reason, not the actual result of _realname_make_name

  $result = _realname_make_name($account);
  if (empty($result)) return $account->name;
  if (!db_result(db_query("SELECT uid from {realname} WHERE uid=%d", $account->uid))) {  
          db_query("INSERT INTO {realname} (uid, realname) VALUES(%d, '%s')", $account->uid, $result);
  } else {
    db_query("UPDATE {realname} SET realname='s' where uid=%d", $result,$account->uid);
  }
  return $result;
}

that was my solution

The changes in #4 worked for me.
Here's a patch.

Thanks

Are you getting errors from a fresh 6.x install on a fresh database, i.e. are you able to reproduce this error or is it just on your database? If you get this on a fresh install I will attempt to reproduce, otherwise I would look at try uninstall/reinstall to see if rebuilding the tables does any good.

Cool, thanks. Let me know if you receive the error again. Thanks.

Can you try making a backup of your realname table, then empty it and then have some users login/logout/login again and see if the problem persists.

Thanks to the previous posters for getting us this far on the bug! The patch in #6 should work, but is incomplete because of a few issues. Specifically:

1. There is a typo in the SQL. "s" should be "%s".
2. Static caching is not being used. A static variable is declared and tested earlier in the function, but the static variable is never actually set.
3. The code always issues a SQL query to either INSERT or UPDATE a record. If, however, the realname was correctly set on a previous page view, then why should the query be repeated on every page call for every user that is loaded?

Since the patch in #6 has already been committed, I am attaching a patch against the latest dev. On my site, implementing the attached patch saves me about 30 database calls per page view, and sometimes more.

-Corey

I wanted to test out this patch but darn PHP 5.3 on my fresh xampplite install is running into Drupal bugs. I will hopefully test this weekend when I can run it on another install.

subscribing

Patch had just one very minor issue of missing a space after a comma, otherwise applied cleanly on Drupal 6.x-1.x-dev. So just re-rolling with the space and going to run it through coder again. If that checks out ok I'm going to set to RTBC and hopefully get a comment from NancyDru before committing.

Sorry that this took so long.

Oops missed the naming standard, so uploading again with full name. Checked patch through coder and no problems were found.

So current status is just want buy-in from NancyDru and then she can commit it or if she wants I can commit it.

With the fixes I have just committed the code is what you show. After the -dev release rolls out, please see if this issue is fixed. If it is not, reopen it.

Using RealName 6.x-1.4 Drupal version 6.20
Received same error. Did the fix not get applied to version 6.x-1.4?