Remove DISTINCT modificator from default scenario
|Reported by:||srokap||Owned by:|
Prevously discuissed here: https://docs.google.com/document/d/1NrxIj4YOTjNbeXDGW3tpz2lNvaRwL2NDPBNd7TgRfFk/edit?disco=AAAAAEr6svk
For properly written queries we shouldn't have to use DISTINCT. Currently we have some stupid joins (see elgg_get_entity_metadata_where_sql n_table join) which make it necessary to use. The least we could do is to parametrize appliance of DISTINCT to allow optimizing queries. I'd love to see NOT using DISTINCT as default policy.