modify user_relationships_update_relationship() to do a db UPDATE instead of DELETE/INSERT so rid's don't change; also put a limit on how many relationships user_relationships_load_all_for_user() will cache, so as not to blow out memcached

refactor code to avoid calling user_relationships_load_all_for_user(), which can be very expensive for users with lots of relatees

refactor user_relationships_block_select_relationships() to avoid calling user_relationships_load_all_for_user()

Index the array returned by user_relationships_relationship_types_load() by rtid. Add user_relationships_load_relationships($criteria = array()) and user_relationships_load_relationships_by_relatee($criteria = array(), $relater = -1) to the API. Update the criteria for counting/loading relationships such that the values of uid, uid1, uid2, rid, requester_id, requestee_id and rtid can be arrays. See http://drupal.org/node/184709.

when approving implying relationships, approve implied relationships regardless of which user requested the implied relationship (http://drupal.org/node/184419). tightened up the code for deleting an implied relationship, and made the if stmts consistent between update and delete.

fix bug in auto-approving relationships; also use new count_api to enforce multiple relationships restriction, if applicable

Add migration of pending buddylist requests. Redo the checkpoint/restart code to make it pretty bulletproof, and to make it easier to restart an aborted migration.

http://drupal.org/node/178621: committing Annette's changes that renamed all user_relationships_message() to user_relationships_get_message(); and added a few new message keys

Invite code is not numeric, so don't test for numeric. Pass code to hook_user by setting it on the form. Only do user_load when necessary.

Pass more information to block theme functions so they have more flexibility in formatting their content (e.g. return NULL for title of an empty block)

Allow admins to specify which node types to display User Relationships blocks on (previously hardcoded to node type 'usernode')

Create implied relationship requests when implying relationship is requested, instead of when implying relationship is approved