Having my own issue and reading many others' issues on duplicate records being returned via multiple field views...
The DISTINCT option is not able to be used in it's current state, if you have multiple fields that need to apply to your results because it applies "DISTINCT" to the whole query.

Since Views is pretty much one giant, complex "Where Clause", shouldn't it correct the issue of not being able to use DISTINCT if there was an option (under DISTINCT) to tell the query which field to apply the DISTINCT rule to?

*My Issue: I am trying to build a complex user profile search form (similar to MySpace) where you have various criteria you can apply to your search. It is working with the exception that I get a result for every single criteria. So if there are 10 criteria to choose from, every single user (that meets that criteria) gets displayed 10 times.

Comments

esmerel’s picture

esmerel commented
Status: Active » Postponed
merlinofchaos’s picture

merlinofchaos commented
Status: Postponed » Closed (won't fix)

DISTINCT can't really be applied per field in most databases. IN D7, it's not even supported, so we won't be doing anything with that in D6.