Re: Query optimize on large database
I'm confused, or the query is: it ...
- selects d2.owner_id
- groups by d1.owner_id
- self-joins on artist and title, not owner_id
- restricts d1.owner_id to one value
Grouping by a column that may have just one value makes no sense. Selecting a column that neither aggregates nor is aggregated will return arbitrary results.
In plain English, what is the query requirement?
Subject
Views
Written By
Posted
1834
July 13, 2016 01:40AM
1071
July 15, 2016 05:12PM
1066
July 16, 2016 04:15AM
1025
July 16, 2016 12:09PM
1045
July 16, 2016 12:36PM
1024
July 16, 2016 02:46PM
Re: Query optimize on large database
1082
July 17, 2016 11:22AM
1040
July 18, 2016 04:28AM
1008
July 18, 2016 08:40AM
998
July 20, 2016 04:46AM
1029
July 20, 2016 08:06AM
1046
July 20, 2016 09:29AM
1029
July 21, 2016 04:35AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.