Allen Pitts
asked on
Oracle query using DISTINCT
Hello expert,
Using the query copied herewith below yields 4758 rows
Running a similar query with
Select DISITNCT PAYER_ID
FROM CCM.CCM_COMPONENT_PRICING
where last_update_user = 1
yields 202 rows.
The 202 rows is needed but with the other fields
resultant from the longer query.
Tried creating a join with short table against the long table
and tried listing all 202 PAYER_IDs in an 'IN' statement
but both grab all of the PAYER IDs
Is there someway to mimic the return of the DISTINCT
query but return the other fields also?
Thanks
Allen in Dallas
++++++++++++++++LONG QUERY++++++++++++++
Select
COMPONENT_PRICING_ID,
COMPONENT_ID,
PAYER_ID,
VARY_BY_MARKET,
COMPONENT_PRICE,
IS_OVERRIDE,
CREATION_USER,
CREATION_DATE,
LAST_UPDATE_USER,
LAST_UPDATE_DATE
from
CCM.CCM_COMPONENT_PRICING
where last_update_user = 1
Using the query copied herewith below yields 4758 rows
Running a similar query with
Select DISITNCT PAYER_ID
FROM CCM.CCM_COMPONENT_PRICING
where last_update_user = 1
yields 202 rows.
The 202 rows is needed but with the other fields
resultant from the longer query.
Tried creating a join with short table against the long table
and tried listing all 202 PAYER_IDs in an 'IN' statement
but both grab all of the PAYER IDs
Is there someway to mimic the return of the DISTINCT
query but return the other fields also?
Thanks
Allen in Dallas
++++++++++++++++LONG QUERY++++++++++++++
Select
COMPONENT_PRICING_ID,
COMPONENT_ID,
PAYER_ID,
VARY_BY_MARKET,
COMPONENT_PRICE,
IS_OVERRIDE,
CREATION_USER,
CREATION_DATE,
LAST_UPDATE_USER,
LAST_UPDATE_DATE
from
CCM.CCM_COMPONENT_PRICING
where last_update_user = 1
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Allen,
I just noticed you posted this in Oracle and Access.
My response is for Oracle. Pat's is for Access.
I just noticed you posted this in Oracle and Access.
My response is for Oracle. Pat's is for Access.
ASKER
Thanks for the code. Works perfectly.
If you really don't care which value of COMPONENT_PRICING_ID for example to return, then use a totals query. Use the Group By argument for the "distinct" columns and choose a different aggregation function for all the other columns, First, Last, Min, Max are all possible or you can use Sum, Avg, etc for numeric fields if those functions make sense.