Summary of Argument only displays correct group for user 1

In case it matters, a sample view definition that exibits the problem:

  $view = new stdClass();
  $view->name = 'applications_school';
  $view->description = 'List of Enrollment Applications by Previous School';
  $view->access = array (
  0 => '6',
  1 => '7',
  2 => '8',
);
  $view->view_args_php = '';
  $view->page = TRUE;
  $view->page_title = 'Applications';
  $view->page_header = '';
  $view->page_header_format = '1';
  $view->page_footer = '<?php
  print $GLOBALS[\'pager_total_items\'][0];
?> Listed';
  $view->page_footer_format = '2';
  $view->page_empty = 'No Applications Found.';
  $view->page_empty_format = '1';
  $view->page_type = 'table';
  $view->url = 'list-applications/school';
  $view->use_pager = TRUE;
  $view->nodes_per_page = '100';
  $view->menu = TRUE;
  $view->menu_title = 'School';
  $view->menu_tab = TRUE;
  $view->menu_tab_default = FALSE;
  $view->menu_tab_weight = '2';
  $view->sort = array (
  );
  $view->argument = array (
    array (
      'type' => 'content: field_previous_school',
      'argdefault' => '4',
      'title' => 'Previous School',
      'options' => '',
      'wildcard' => 'all',
      'wildcard_substitution' => 'all',
    ),
  );
  $view->field = array (
    array (
      'tablename' => 'node',
      'field' => 'title',
      'label' => 'Name',
      'handler' => 'views_handler_field_nodelink',
      'sortable' => '1',
      'defaultsort' => 'ASC',
      'options' => 'link',
    ),
    array (
      'tablename' => 'node_data_field_grade_applying',
      'field' => 'field_grade_applying_value',
      'label' => 'Grade',
      'handler' => 'content_views_field_handler_ungroup',
      'sortable' => '1',
      'options' => 'default',
    ),
    array (
      'tablename' => 'node_data_field_enrolled',
      'field' => 'field_enrolled_value',
      'label' => 'Enrolled',
      'handler' => 'content_views_field_handler_ungroup',
      'sortable' => '1',
      'options' => 'default',
    ),
    array (
      'tablename' => 'node_data_field_previous_school',
      'field' => 'field_previous_school_value',
      'label' => 'Previous School',
      'handler' => 'content_views_field_handler_ungroup',
      'sortable' => '1',
      'options' => 'trimmed',
    ),
    array (
      'tablename' => 'users',
      'field' => 'name',
      'label' => 'Submitter',
      'sortable' => '1',
    ),
    array (
      'tablename' => 'node_data_field_mother',
      'field' => 'field_mother_value',
      'label' => 'Parent #1',
      'handler' => 'content_views_field_handler_ungroup',
      'sortable' => '1',
      'options' => 'trimmed',
    ),
    array (
      'tablename' => 'node',
      'field' => 'created',
      'label' => 'Date',
      'handler' => 'views_handler_field_date_custom',
      'sortable' => '1',
      'options' => 'dMy',
    ),
  );
  $view->filter = array (
    array (
      'tablename' => 'node',
      'field' => 'type',
      'operator' => 'OR',
      'options' => '',
      'value' => array (
  0 => 'content_enrollment_application',
),
    ),
    array (
      'tablename' => 'node_data_field_school_year',
      'field' => 'field_school_year_value_default',
      'operator' => 'OR',
      'options' => '',
      'value' => array (
  0 => '2008-2009',
),
    ),
    array (
      'tablename' => 'node_data_field_special_education',
      'field' => 'field_special_education_value_default',
      'operator' => 'OR',
      'options' => '',
      'value' => array (
  0 => 'No.',
),
    ),
  );
  $view->exposed_filter = array (
    array (
      'tablename' => 'node_data_field_school_year',
      'field' => 'field_school_year_value_default',
      'label' => 'School Year',
      'optional' => '0',
      'is_default' => '1',
      'operator' => '0',
      'single' => '0',
    ),
    array (
      'tablename' => 'node_data_field_special_education',
      'field' => 'field_special_education_value_default',
      'label' => 'Special Education',
      'optional' => '1',
      'is_default' => '0',
      'operator' => '0',
      'single' => '0',
    ),
  );
  $view->requires = array(node, node_data_field_grade_applying, node_data_field_enrolled, node_data_field_previous_school, users, node_data_field_mother, node_data_field_school_year, node_data_field_special_education);
  $views[$view->name] = $view;

Ignore the warning in the above. Apparently the code filter doesn't like backslashes in that combination of characters.

It appears that the distinct is added by line 2536 of node.module (v 1.641.2.32):

/**
 * Implementation of hook_db_rewrite_sql
 */
function node_db_rewrite_sql($query, $primary_table, $primary_field) {
  if ($primary_field == 'nid' && !node_access_view_all_nodes()) {
    $return['join'] = _node_access_join_sql($primary_table);
    $return['where'] = _node_access_where_sql();
    $return['distinct'] = 1;
    return $return;
  }
}

Changing the 1 to a 0 for distinct solves the problem. Obviously this may not be a solution until someone more familiar with the core node module lets us know if there is another way to solve whatever problem they were solving by adding distinct in the first place.

There may be a way to use hook_db_rewrite_sql in the cck module to set distinct=0 under the correct conditions and somehow ensure it's run after node.module's function.

Rather, I just had the belated realization that while the code listed above sets distinct=1, changing it to 0 may simply be overriding the actual original cause elsewhere in the permissions checking by forcing it to a 0 in a later hook.

Is there anything unique about a views node table summary query (since the query is passed into the function) that could be used in a views_db_rewrite_sql function to check for it and set distinct=0 in that case, overriding the node.module's setting distinct=1?

Otherwise, you could set a variable just before calling db_rewrite_sql that could then be referenced by views_db_rewrite_sql to set distinct=0.... I'd have to think about how the variable scope would have to work in that case. I know you're already using a no_distinct reference in various places, but I'm not sure the value is currently referenceable in the scope views_db_rewrite_sql would be in, since I still haven't fully figured out how everything in the views module connects.

I tried a few tests creating a views_db_rewrite_sql function to set distinct=0 and couldn't get it to fire and override properly, even though the views weight in the system table is 10.

So I suppose for now I'll disable the cac_lite module so that there aren't any node_access modules in the system to cause the distinct in node.module to fire.

As you say, _sigh_.