Bidirectional relationship data not retrieved correctly with 'select' when using term_id

[CPapadim]

I'm not exactly sure how this happened. I have a bidirectional relationship, let's say authors and books. The 'authors' type is a custom taxonomy while the 'books' type is a custom post type. I added a new image field to 'authors' content type, populated that field with temporary data for all instances of that content type, and then later updated that data in that image field with yet newer (production) data.

At some point in the above process, the 'books' bidirectional relationship was corrupted. Although the related books all showed up correctly in the admin edit view, when querying against them using select, t.ID returned back the id of the first related book. What's interesting is that it returned the correct number of related books, but just the t.ID was all the same t.ID, that of the first 'book'.

Re-saving the author content type seems to have repaired the issue and now t.ID is returning back all of the different IDs, but ONLY for those authors that have been re-saved.

It's unclear to me which of the above things I did with field creation, or something entirely unrelated, caused the issue.

[CPapadim]

Update - After fixing it above, i updated pods to 2.71 and it caused the issue again.

So for sure the update from 2.70 beta to 2.71 is one of the ways to cause it since that's all I did this time

[CPapadim]

Another update -
It appears it is actually unrelated to anything I'm doing. It happened again at random. I changed my query from:

        $params = array(        'select' => 't.term_id, field_name.id  AS field_id',
                                'where' => 't.term_id = ' . $obj_id,
                                'limit' => -1
                        );

to remove the t.term_id:

        $params = array(        'select' => 'field_name.id  AS field_id,
                                'where' => 't.term_id = ' . $obj_id,
                                'limit' => -1
                        )

And that appears to also fix it, but I wonder for how long . I don't have any cache plugins running at the moment so it isn't that. But it seems related to the above query not returning the right results some of the time, even though the stored data in the database SHOULD be correct (since the correct result returns automatically when I do things like change the query).

Just to be clear, the incorrectly retrieved value in the query above is field_name.id, where field_name is the relationship field that exists on teh custom taxonomy.

Quite confused.

[CPapadim]

Looks like when i remove t.term_id from the query or if i alias it as something else (e.g. tid), it works, but it increases the number of queries the page does by quite a bit. So I suspect the error causing this issue is in whatever optimizations are happening in the query when t.term_id is used perhaps in some sort of join with other tables.

[CPapadim]

Getting the same issue in a non-taxonomy query when including t.ID and and other relationship fields, e.g.:

'select' => 't.ID, field_name_rel1.field_name_rel2.post_title AS value'

In this case field_name_rel1 is a single-valued relationship field, which has another relationship field in it named field_name_rel2, that is multi-valued. The values retrieved for that second field are always the first entry if I include t.ID in the query, so if there's 6 values in the multi-value field, it retrieves the first value 6 times. If I alias t.ID as something, or if i don't include it at all, I get back the values I expect.