Something's not right here.

I was debugging some strange behaviour where a view showing one row of content via a Relation relationship from one node to another was showing nothing. (One node with one relation linking it to one other node, simple case)

I added a "relation: rid" field and removed the 'one row' limitation. It turns out views was finding two relations for this one node where only one existed: one had the correct rid and linked to the content correctly, the other had a rid of 0 and went nowhere.

How could Relation's views integration relationship feature find a relation for an entity that has a rid of 0? Seems crazy to me, no idea where to start debugging this. What should I look at, what are the possibilities?

The patch at #1396678: RID not saved in revision table when new relation is saved was applied well before any of the relations in question were created, so it's not that.

Comments

Jorrit’s picture

Jorrit commented

What is the query that is generated by Views?

mikran’s picture

mikran commented
Status: Active » Postponed (maintainer needs more info)

Is this still an issue after #1444800: Duplicate entries in view with node to node relationships?

naught101’s picture

naught101 commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing as no new info provided. Also, all relations have an endpoint with rid=0. PHP uses zero-based indexing. See http://c2.com/cgi/wiki?ZeroAndOneBasedIndexes