In a very rare circumstance, having 2 or more relationships can block a normal table of the same name from adding.

In particular, if you have two 'user reference' relationships, fields from the implied node-->user reference stop working.

This is related to: http://drupal.org/node/385988

CommentFileSizeAuthor
#1 386986-relationships.patch1.77 KBmerlinofchaos

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Needs review
StatusFileSize
new 386986-relationships.patch1.77 KB
dww’s picture

dww
we/he/they
commented

I applied this on d6.d.o and it seems to work great on all the views I tested (all of the issue views).

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Fixed

Finally committed.

dww’s picture

dww
we/he/they
commented
Issue tags: +needs drupal.org deployment

Excellent, thanks! Now I just need to deploy a new copy of views on d.o and #385988: "Submitted by" filter only showing tickets assigned to the requested user will be fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

dww’s picture

dww
we/he/they
commented
Issue tags: -needs drupal.org deployment

Just upgraded d.o to 6.x-2.5, so this is totally resolved... yay.

dww’s picture

dww
we/he/they
commented

Ugh, this broke things in some cases. :( See #433290: Fatal SQL errors caused by broken table aliases in some cases in add_relationships()