Distinct doesn't work when sorting by field with multiple values

Sure, there is no reason it should work.

It's just not possible to sort by a fieldapi field without joining it.
If you join it, you can't get rid of the duplicates. That's IMPOSSIBLE. Either choose to use sort or not.

You could for example use hook_views_pre_render and alter $view->result.

In general at least from my perspective an event has just a single date, no multiple, but i might be wrong.

drcho: Thanks *very* much for posting that solution. It's clean, it works, and it doesn't mess with the SQL. It's a great way to say "I don't want any node displayed more than once in this view". Honestly, I rarely want a node duplicated in a view so I agree that this would be a good addition to views as an option. DISTINCT is just too flaky and most users just want the dups removed.

@drcho: Thanks a lot, exactly what I was looking for.
@dereine: I am listing opera productions, with identical performances on different days (identical for the purpose of the web-site). So in this case, the same general event has several dates.

So this issue seems to be fixed.

The code in #6 works but unfortunately does not recounts the pager.

@drcho
Don't complain... make a proper issue, with a good patch etc.
If you complain that we aren't doing enough, feel free to help on other issues as well.

Don't want to be disrespectful, but I'd like to open this issue again in the hopes that someone might be able to figure out a fix. I think this problem might come up frequently on arts or performance related websites; I'm currently working on a choreographer's site and most of her performances have multiple dates and times, similarly to what ursula mentions in #8.

I've not been able to figure out my own fix yet, but I will try to come up with a patch for this if no one else figures it out first!

Well read http://drupal.org/node/1223448#comment-4755566 first, i think you are kind of lost here.

works ok but it shows some nodes in each page. Once in page 1, once in page 2,...
Any ideas?

I was just checking, but cant we put the code in #6 in the view header? I tried but it seems I can't alter the $results...

I would like to give 1 million thank yous to @drcho for this solution. I've been struggling with this for a few months! You are a hero!

A much more current issue related to this is here: http://drupal.org/node/1765730

#6 worked for me.

Hopefully this will be fixed soon.

.

I tweaked #6 to keep the internal index in sync with the new array. Otherwise, the last row was not displaying its content for me.

/*
* implements hook_view_pre_render()
*/
function mytheme_views_pre_render(&$view)
{
  switch($view->name)
  {
    case 'no_double_nodes_view':
      $nids = array(); // array of nodes to prevent duplicates
      $resultNoDoubleNodes = array(); // manipulated results
      $skipped = 0;
      foreach($view->result as $key => $result) // check each node of the result array on it's nid
      {
        $nid = $result->nid;
        if (!in_array($nid, $nids)) // if this node isn't a duplicate
        {
          $view->result[$key]->index = ($key - $skipped);
          $resultNoDoubleNodes[] = $view->result[$key]; // add it to the manipulated results
          $nids[$key] = $nid; // mark this nid as in results to prevent duplicates from now on
        } else {
          $skipped++;
        }
      }
      $view->result = $resultNoDoubleNodes; // replace the old results with the results without duplicates
      break;
    default:
      break;
  }
}

Thanks @sbreese ,, #23 works fine :)

@drcho

Your solution worked for me. But it didn't work on xls export view.

Many Thanks anyway
:)

Hi,
has anybody tried to turn on aggregation for the view? Distinct then works for me.

For date field with multiple values This worked for me:

In Filter Criteria, I added "Content: Date:delta (= 0)"

Edit: Sorry. It did work not for this reason:
In particular, if you are filtering by upcoming dates and the field's first date (delta 0) is in the past but subsequent dates are in the future, no row will be returned.

#23 "works" in the way that it removes duplicates, but my view is setup to display 18 items and when using this method, I get 18 results minus the removed duplicates.