Create 2 relationship types: test1 and test 2. Have test2 imply test1. Delete test1. The relevant row in the user_relationship_implications table will not be deleted. This doesn't affect any functionality, since relationship type id's are never reused, but it would be nice to clean up the implications table when types are deleted.

CommentFileSizeAuthor
#1 urideltype.patch1.04 KBprfctns6@gmail.com
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

prfctns6@gmail.com’s picture

Priority: Minor » Normal
FileSize
1.04 KB

Actually, it turns out this does affect functionality, as follows:

Create 2 relationships, test1 and test2, and have test2 imply test1. Delete test1. Then create and approve a relationship of type test2. Since the row is still in the implications table, approving the test2 relationship will create a new relationship; however, because relationship type test1 no longer exists, the new relationship will have an rtid of 0. This results in extraneous, odd looking relationships on the 'view all relationships' page.

Attached is a patch that cleans up the implications table when a type is deleted.

sprsquish’s picture

Status: Active » Closed (fixed)