Query access fails in certain cases on post-RC1 Views

commit 0b273e947fd290bc50ce758ca54437210f95cc41
Author: Daniel Wehner <daniel.wehner@erdfisch.de>
Date:   Sun Aug 28 16:54:17 2011 +0200

    #1222324 by dereine: Apply access tags of relationships to the query

diff --git a/handlers/views_handler_relationship.inc b/handlers/views_handler_relationship.inc
index 3b5c9fa..6bd54b3 100644
--- a/handlers/views_handler_relationship.inc
+++ b/handlers/views_handler_relationship.inc
@@ -123,6 +123,12 @@ class views_handler_relationship extends views_handler {
     $alias = $def['table'] . '_' . $this->table;
 
     $this->alias = $this->query->add_relationship($alias, $join, $this->definition['base'], $this->relationship);
+
+    // Add access tags if the base table provide it.
+    if (empty($this->query->options['disable_sql_rewrite']) && isset($table_data['table']['base']['access query tag'])) {
+      $access_tag = $table_data['table']['base']['access query tag'];
+      $this->query->add_tag($access_tag);
+    }
   }

We create a line item view. We add a relationship to an order.
Then Views adds both the query tag for line items, and the query tag for orders.
The query tag for line items already handles the access for orders, calling commerce_entity_access_query_alter() for commerce_order
with the appropriate base table. The problem is in the second, extra tag that now gets added.

In that case, commerce_entity_access_query_alter() gets called for commerce_order, but without the base table specified.
So the base views table gets taken instead, leading to a condition on "commerce_line_item.uid" instead of "commerce_order.uid", which fails because line items don't have a uid column.