Correlated subquery help

Hi I've the following tables and the requirement
create table test1 (id number,rk varchar2(11),rk_cd varchar2(11))
create table test2 (id number,rk1 varchar2(11),rk_cd1 varchar2(11))
insert into test1 values(1,'I+','LG')
insert into test1 values(2,'I-','SH')
insert into test2 values(1,'I+','LG')
insert into test2 values(1,'I+','LG')for a single id in TEST1 Table there could be multiple rows in TABLE2, so i need to get the matching records in both tables
I tried the folloiwng query to achieve the same
select * from test1
where (rk,rk_cd) = all (select NVL(rk1,'X'),NVL(rk_cd1,'X')
                  from test2
            where TEST1.ID=test2.id  The above query is returning me even the id=2 , where id=2 doesn't exist in TEST2
Could you hint me the changes i need to do in subquery.
Expected output
Only id=1 record Thank you

Hi,
Perhaps you meant to say ANY instead of ALL:
SELECT  *
FROM      test1
WHERE  (rk, rk_cd) = ANY (
                              SELECT  NVL (rk1,    'X')
                   ,         NVL (rk_cd1, 'X')
                           FROM    test2
                     WHERE   test1.id     = test2.id 
;Most people would use "IN" rather than "= ANY".
Do you really mean what you're saying with NVL? If that's important, then include some examples in the sample data and results where it matters. For example:
INSERT INTO  test1 (id, rk, rk_cd) VALUES  (3, 'I+', 'X');
INSERT INTO  test2 (id, rk1, rk_cd1) VALUES  (3, 'I+', NULL);Edited by: Frank Kulash on Jul 9, 2012 6:15 AM

Similar Messages

  • Top n Analysis using correlated subquery

    Please explain this query. It is doing top n analysis using correlated subquery. I need explaination of execution of this query.
    Select distinct a.sal
    From emp a
    where 1=(select count ( distinct b.sal) from emp b
         where a.sal <=b.sal)
    Thanks in advance

    Try breaking the query down and rewriting it in order to follow the logic;
    SQL> --
    SQL> -- Start by getting each salary from emp along with a count of all salaries in emp
    SQL> --
    SQL> select   a.sal,
            (select count (distinct b.sal) from scott.emp b ) count_sal
    from scott.emp a
    order by 1 desc
           SAL  COUNT_SAL
          5000         12
          3000         12
          3000         12
          2975         12
          2850         12
          2450         12
          1600         12
          1500         12
          1300         12
          1250         12
          1250         12
          1100         12
           950         12
           800         12
    14 rows selected.
    SQL> --
    SQL> --Add a condition to the count for only salaries below or equal to the current salarySQL> --
    SQL> select   a.sal,
            (select count (distinct b.sal) from scott.emp b where a.sal <=b.sal) rank_sal
    from scott.emp a
    order by 1 desc
           SAL   RANK_SAL
          5000          1
          3000          2
          3000          2
          2975          3
          2850          4
          2450          5
          1600          6
          1500          7
          1300          8
          1250          9
          1250          9
          1100         10
           950         11
           800         12
    14 rows selected.
    SQL> --
    SQL> -- Add a condition to only pick the nth highest salary
    SQL> --
    SQL> select    a.sal,
             (select count (distinct b.sal) from scott.emp b where a.sal <=b.sal) rank_sal
    from scott.emp a
    where (select count (distinct b.sal) from scott.emp b where a.sal <=b.sal) = 4
           SAL   RANK_SAL
          2850          4
    1 row selected.Hope this helps.

  • JDOQL Correlated Subquery - Bad SQL

    Hi,
    When I execute a JDOQL correlated subquery, the generated SQL is either
    invalid or incorrect. Exactly what happens depends on the exact query, and
    on the target database type, but I believe it all stems from the same
    problem, which has to do with table aliasing.
    If you need further details to reproduce this, please let me know. I'll be
    glad to help in any way I can to get this situation remedied quickly, as I
    am depending on this functionality. I have a test application to
    demonstrate the problem.
    I'm using Kodo 3.3.3 and application identity.
    Paul Mogren
    CommerceHub

    For the record, this is in part due to a bug in Kodo's SQL92 joining.
    See http://bugzilla.solarmetric.com/show_bug.cgi?id=1156
    -Patrick
    Paul Mogren wrote:
    Certainly... Here's a simple example using Microsoft's JDBC Driver for SQL
    Server 2000, and kodo.jdbc.sql.SQLServerDictionary, which produces invalid
    SQL.
    The query:
    pm.newQuery(Container.class,
    "(select from Entry entry where entries.contains(entry) &&
    entry.containedId != 1).isEmpty()");
    The classes:
    class Contained {
    private int id; //pk
    class Container {
    private int id; //pk
    private Set entries = new HashSet(); //<Entry>
    class Entry {
    private int containerId; //pk
    private int containedId; //pk
    private Container container; //persistent-redundant
    private Contained contained; //persistent-redundant
    The result:
    Incorrect syntax near the keyword 'WHERE'. {prepstmnt 31598780 SELECT
    t0.container_id, t0.lock FROM  WHERE (NOT EXISTS (SELECT DISTINCT
    t2.contained_id, t2.container_id FROM dbo.entry t2 WHERE (t1.contained_id
    = t2.contained_id AND t1.container_id = t2.container_id AND
    t2.contained_id <> ?) AND t0.container_id = t1.container_id))
    [params=(int) 1]} [code=156, state=HY000]
    Patrick Linskey wrote:
    Hi Paul,
    Kodo's correlated subquery support does have some known limitations. Can
    you post a sample JDOQL statement + corresponding SQL statement?
    -Patrick
    Paul Mogren wrote:
    Hi,
    When I execute a JDOQL correlated subquery, the generated SQL is either
    invalid or incorrect. Exactly what happens depends on the exact query, and
    on the target database type, but I believe it all stems from the same
    problem, which has to do with table aliasing.
    If you need further details to reproduce this, please let me know. I'll be
    glad to help in any way I can to get this situation remedied quickly, as I
    am depending on this functionality. I have a test application to
    demonstrate the problem.
    I'm using Kodo 3.3.3 and application identity.
    Paul Mogren
    CommerceHub

  • Correlatd Subquery help needed for 8i

    Hi Everyone,
    I am struggling with a correlated subquery, the individual parts of which work fine, but not together! I am guessing that this is something to do with the SQL implementation in Oracle 8i and the way that it handles table references, but I am not sure how to approach this for a workable solution. Any help would be greatly appreciated.
    Here is my SQL:
    select
    TA.JAHR as yr,
    TB.WOCHE as week,
    (select count(*) from (
    SELECT T2.JAHR
    , T2.KUNDEN_ID
    , CDW.PRODUKTE.EAN_VBE
    , T3.WOCHE
    , Sum(T2.ANZ_VSE)
    FROM CDW.RECHNUNGSPOSITIONEN T2
    JOIN CDW.PRODUKTE ON CDW.PRODUKTE.ID = T2.PRODUKT_ID
    JOIN CDW.KALENDER T3 ON T3.DATUM = T2.RECHNUNG_DATUM
    WHERE T2.JAHR = TA.JAHR
    AND CDW.PRODUKTE.SEGMENT Like 'PET%'
    AND T3.WOCHE = TB.WOCHE
    AND T2.AUFTRAGS_ART_ID NOT IN (39,48)
    AND CDW.PRODUKTE.EAN_VBE <> 0
    GROUP BY T2.JAHR
    , T2.KUNDEN_ID
    , T3.WOCHE
    , CDW.PRODUKTE.EAN_VBE
    )) as qty
    FROM
    CDW.RECHNUNGSPOSITIONEN TA
    JOIN
    CDW.KALENDER TB ON TB.DATUM = TA.RECHNUNG_DATUM
    WHERE
    TA.JAHR >= 2005
    GROUP BY
    TA.JAHR,
    TB.WOCHE
    It looks as though the inner query cannot use the table references in the outer query. Am I missing something?
    Cheers and thanks in advance
    The Frog

    The SQL Standard defines correlation variables at only one level deep. In your case you were trying to reference a table (TA and TB) at the 2nd level. In this case it may be easier to remove this inline subquery altogether. I tried to simplify your query. This is just a guess and it's not tested:
    SELECT  TA.JAHR as yr
    ,       TB.WOCHE as week
    ,       COUNT(*) as qty
    FROM    CDW.RECHNUNGSPOSITIONEN TA
    JOIN    CDW.KALENDER            TB      ON TB.DATUM             = TA.RECHNUNG_DATUM
    JOIN    CDW.RECHNUNGSPOSITIONEN T2      ON TA.JAHR              = T2.JAHR
    JOIN    CDW.PRODUKTE                    ON CDW.PRODUKTE.ID      = T2.PRODUKT_ID
    JOIN    CDW.KALENDER            T3      ON T3.DATUM             = T2.RECHNUNG_DATUM
                                           AND T3.WOCHE             = TB.WOCHE
    WHERE   CDW.PRODUKTE.SEGMENT Like 'PET%'
    AND     T2.AUFTRAGS_ART_ID NOT IN (39,48)
    AND     CDW.PRODUKTE.EAN_VBE != 0
    AND     TA.JAHR >= 2005
    GROUP BY        TA.JAHR
    ,               TB.WOCHEIt's always helpful to post the following:
    1. FULL Oracle version (SELECT * FROM V$VERSION)
    2. Sample data in the form of CREATE / INSERT scripts.
    3. Expected output.
    4. Explanation on how to achieve expected output.
    5. Please use \ tags to surround anything that requires fixed-width spacing like SQL statements.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • SQL Bug in "Minus" in correlated subquery presence of index (11.2.0.1.0)

    SQL Bug in "Minus" in correlated subquery presence of index
    (Oracle Database 11g Release 11.2.0.1.0)
    Below, there is a small example that shows the bug. Further below,
    there are some more comments.
    drop table Country;
    create table Country
    (code VARCHAR2(4) constraint countrykey PRIMARY KEY,
    name VARCHAR2(35));
    -- if the key constraint is not given, the bug does not occur
    drop table City;
    create table City
    (name VARCHAR2(35),
    country VARCHAR2(4),
    population number);
    drop table Locatedon;
    create table Locatedon
    (city VARCHAR2(35),
    country VARCHAR2(4),
    island VARCHAR2(35));
    insert into country values('E','Spain');
    insert into country values('F','France');
    insert into country values('S','Sweden');
    insert into country values('GB','Sweden');
    insert into city values('Ajaccio','F',53500);
    insert into city values('Paris','F',2152423);
    insert into city values('Palma','E',322008);
    insert into city values('Madrid','E',3041101);
    insert into city values('Stockholm','S',711119);
    insert into city values('London','GB',6967500);
    insert into locatedon values('Ajaccio','F','Corse');
    insert into locatedon values('Palma','E','Mallorca');
    insert into locatedon values('London','GB','Great Britain');
    -- all countries that have a city that is not located on
    -- some island: should be E, F, S.
    Select c.name
    From country c
    Where exists
    ((Select name
    From city
    Where city.country=c.code)
    minus
    (Select city
    From locatedon
    Where locatedon.country=c.code)
    -- wrong answer: only Sweden; Spain and France not in the answer!
    select distinct country from
    ((Select name, country
    From city)
    minus
    (Select city, country
    From locatedon)
    -- correct answer: E, F, S
    Comments:
    The bug has been found by students in our SQL course.
    Using a larger database from that course, the bug can be reproduced
    (same queries as above) at
    http://www.semwebtech.org/sqlfrontend/
    (wrong: 142 answers, correct: 154 answers)
    During reducing it to a simple sample, there were some interesting
    observations: trying with smaller and simpler tables (without the keys)
    and synthetic data, the bug did not occur immediately. When
    restating the query after about one day, the bug occurred. Obviously,
    Oracle creates some index on its own in course of its internal
    optimization that (or more exactly, its usage) exhibits the bug. The
    query plan (showed in SQL Developer) was the same before and after.
    Wolfgang

    There's a typo in the test data - GB should presumably not be in Sweden. However....
    the bug did not occur immediatelyIt's possible. But what would have almost certainly happened is that the execution plan DID change at some point. There are various reasons why it might not be immediate.
    Obviously, Oracle creates some index on its own in course of its internal optimizationFar from obvious, what are you on about?
    The query plan was the same before and afterBet you it wasn't.
    A clear illustration of the issue and indication that it must be a bug is below.
    Simply by hinting a different access method, we can change the result. Therefore, bug.
    See [url http://support.oracle.com]Oracle Support and search for "wrong results".
    Please raise with Oracle Support to get confirmation of bug.
    There have been so many wrong results bugs recently, it's getting ridiculous.
    It's a real issue, IMHO.
    If you can't trust the DB to get your data right....
    Note that the query plan is very much NOT the same and it is the difference in query plan which s that is the root cause of the bug.
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    PL/SQL Release 11.2.0.2.0 - Production
    CORE    11.2.0.2.0      Production
    TNS for Linux: Version 11.2.0.2.0 - Production
    NLSRTL Version 11.2.0.2.0 - Production
    SQL> SELECT c.name
      2  FROM   country1 c
      3  WHERE  exists ((SELECT name
      4                  FROM   city1
      5                  WHERE  city1.country=c.code)
      6                  MINUS
      7                 (SELECT city
      8                  FROM   locatedon1
      9                  WHERE  locatedon1.country=c.code));
    NAME
    Sweden
    SQL> SELECT /*+ full(c) */
      2         c.name
      3  FROM   country1 c
      4  WHERE  exists ((SELECT name
      5                  FROM   city1
      6                  WHERE  city1.country=c.code)
      7                  MINUS
      8                 (SELECT city
      9                  FROM   locatedon1
    10                  WHERE  locatedon1.country=c.code));
    NAME
    Spain
    France
    Sweden
    SQL> explain plan for
      2  SELECT c.name
      3  FROM   country1 c
      4  WHERE  exists ((SELECT name
      5                  FROM   city1
      6                  WHERE  city1.country=c.code)
      7                  MINUS
      8                 (SELECT city
      9                  FROM   locatedon1
    10                  WHERE  locatedon1.country=c.code));
    Explained.
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 156929629
    | Id  | Operation                    | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT             |            |     1 |    27 |    12  (25)| 00:00:01 |
    |   1 |  NESTED LOOPS                |            |       |       |            |          |
    |   2 |   NESTED LOOPS               |            |     1 |    27 |    12  (25)| 00:00:01 |
    |   3 |    VIEW                      | VW_SQ_1    |     6 |    24 |    10  (20)| 00:00:01 |
    |   4 |     MINUS                    |            |       |       |            |          |
    |   5 |      SORT UNIQUE             |            |     6 |   138 |            |          |
    |   6 |       TABLE ACCESS FULL      | CITY1      |     6 |   138 |     4   (0)| 00:00:01 |
    |   7 |      SORT UNIQUE             |            |     3 |    69 |            |          |
    |   8 |       TABLE ACCESS FULL      | LOCATEDON1 |     3 |    69 |     4   (0)| 00:00:01 |
    |*  9 |    INDEX UNIQUE SCAN         | COUNTRYKEY |     1 |       |     0   (0)| 00:00:01 |
    |  10 |   TABLE ACCESS BY INDEX ROWID| COUNTRY1   |     1 |    23 |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       9 - access("VW_COL_1"="C"."CODE")
    Note
       - dynamic sampling used for this statement (level=4)
    26 rows selected.
    SQL> explain plan for
      2  SELECT /*+ full(c) */
      3         c.name
      4  FROM   country1 c
      5  WHERE  exists ((SELECT name
      6                  FROM   city1
      7                  WHERE  city1.country=c.code)
      8                  MINUS
      9                 (SELECT city
    10                  FROM   locatedon1
    11                  WHERE  locatedon1.country=c.code));
    Explained.
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 1378726376
    | Id  | Operation            | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT     |            |     1 |    23 |    14  (15)| 00:00:01 |
    |*  1 |  FILTER              |            |       |       |            |          |
    |   2 |   TABLE ACCESS FULL  | COUNTRY1   |     4 |    92 |     4   (0)| 00:00:01 |
    |   3 |   MINUS              |            |       |       |            |          |
    |   4 |    SORT UNIQUE       |            |     1 |    23 |     5  (20)| 00:00:01 |
    |*  5 |     TABLE ACCESS FULL| CITY1      |     1 |    23 |     4   (0)| 00:00:01 |
    |   6 |    SORT UNIQUE       |            |     1 |    23 |     5  (20)| 00:00:01 |
    |*  7 |     TABLE ACCESS FULL| LOCATEDON1 |     1 |    23 |     4   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       1 - filter( EXISTS ( (SELECT "NAME" FROM "CITY1" "CITY1" WHERE
                  "CITY1"."COUNTRY"=:B1)MINUS (SELECT "CITY" FROM "LOCATEDON1" "LOCATEDON1"
                  WHERE "LOCATEDON1"."COUNTRY"=:B2)))
       5 - filter("CITY1"."COUNTRY"=:B1)
       7 - filter("LOCATEDON1"."COUNTRY"=:B1)
    Note
       - dynamic sampling used for this statement (level=4)
    27 rows selected.Just to show that it's related to query transformation:
    SQL> SELECT /*+ 
      2             no_query_transformation
      3         */
      4         c.name
      5  FROM   country1 c
      6  WHERE  exists ((SELECT name
      7                  FROM   city1
      8                  WHERE  city1.country=c.code)
      9                  MINUS
    10                 (SELECT city
    11                  FROM   locatedon1
    12                  WHERE  locatedon1.country=c.code));
    NAME
    Spain
    France
    Sweden
    SQL> Edited by: Dom Brooks on Jun 30, 2011 2:50 PM

  • Performance of using a Select For Update vs a correlated subquery

    I was wondering wether or not it is more effecient to use the
    Select ... For Update (with a cursor etc.) versus a correlated
    subquery.
    I can accomplish the same thing with either however performance
    at our site is an issue.

    Use select for update cursor as that is faster as it updates
    based on the rowid. One thing to keep in mind is that rowid is
    session specific and the rows to be updated get locked so that
    nobody else can update them till the lock is released. I have
    had very good performance results with these cursors.
    Good luck !
    Sudha

  • How does oracle execute a correlated subquery .... some confusion

    How does oracle 10g execute a correlated subquery?
    I read some articles online & i am a little confused.
    example:
    select * from emp e
    where e.deptno in (select d.deptno from dept d
    where e.deptno = d.deptno);
    My questions .......
    1.In the above example, does oracle read the entire outer table first and then run the inner query using the rows returned by the outer query?
    I read in some articles that they execute simultaneously.
    How does this work?
    2.Should the inner query have lesser amount of rows compared to the outer query for a good performance?
    3.Can every correlated subquery be converted to a join and if so which one to use?
    Truly appreciate any inputs on how oracle executes it at the backend.
    Thanks in advance.

    user10541890 wrote:
    How does oracle 10g execute a correlated subquery?
    I read some articles online & i am a little confused.
    example:
    select * from emp e
    where e.deptno in (select d.deptno from dept d
    where e.deptno = d.deptno);
    My questions .......
    1.In the above example, does oracle read the entire outer table first and then run the inner query using the rows returned by the outer query?
    I read in some articles that they execute simultaneously.
    How does this work?SQL is not a procedural language. SQL code specifies what the system sill do, not how the system wlll do it; that's entirely up to the system.
    What does it matter to you whether the two are done together, or if one is completed before the other begins?
    The system will probably choose to run ucorellated subqueiris only once, and correlated queries multiple times as needed.
    2.Should the inner query have lesser amount of rows compared to the outer query for a good performance?That usually doesn't matter.
    It some cases, you may want to consider whether the subquery is correlated or not. If the subquery is very costly, and produces, say, 1 million rows, but you know the main query will only produce about 5 rows, then you may want to do a correlated subquery rather than an uncorrelated one.
    3.Can every correlated subquery be converted to a join and if so which one to use?I believe so.
    Use whichever is easier to code and debug. That will change depnding on the data and the requirements.
    If performance is an issue, try different ways. Usually, where I've noticed a big difference, join was fastest.
    By the way, it's unusual to have a correlated IN-subquery.
    Usually IN-subqueris are uncorrelated, like this:
    select  *
    from      emp     e
    where     e.deptno     in ( select  d.deptno
                        from    dept     d
                      );(This and the queries below produce the same resutls as your original query.)
    Correlated subqueries are usually used for scalar subqueries or EXISTS subqueries, like this:
    select  *
    from      emp     e
    where     EXISTS ( select  d.deptno
               from    dept     d
                    where   e.deptno = d.deptno
                );To do the same thing with a join:
    select  e.*
    from      emp     e
    join     dept     d     on     e.deptno     = d.deptno
    ;assuming dept.deptno is unique.

  • Difference between a regular subquery and a correlated subquery

    Can someone explain EXACTLY what is a correlated subquery and could you give me an example? I'm taking an Oracle DBA class and I would appreciate your feedback. Thanks. :)

    "Normal" subquery (the subquery is executed only once for the statement):
    select name
    from emp
    where salary > (select avg(emp2.salary) from emp emp2);
    Correlated subquery (it is executed for each row of the main query):
    select name
    from emp
    where salary > (select avg(salary) from emp emp2
    where emp2.deptno = emp.deptno);
    Can someone explain EXACTLY what is a correlated subquery and could you give me an example? I'm taking an Oracle DBA class and I would appreciate your feedback. Thanks. :)

  • Help with a correlated subquery. flawed results..

    Hi,
    Can anyone tell me what I am doing wrong here? I am trying to get the employees whos have above average salarys for there departments.
    SELECT first_name||' '||last_name  NAME,
           department_id,
           salary
    FROM employee
    WHERE salary > (SELECT AVG (salary)
                    FROM employee
                    GROUP BY department_id);I run this and get this:
    ORA-01427: single-row subquery returns more than one rowHow can I amend this subquery to work for my needs? if i leave off:
    GROUP BY department_idthen it gives the average for all employees.
    Thanks!
    Message was edited by:
    user526807

    Your sub-query is not really correlated.
    You should join it by deptno with exetrnal query
    SELECT ename||' '||job,
           deptno,
           sal
    FROM scott.emp e
    WHERE sal > (SELECT AVG (sal)
                    FROM scott.emp
                    where deptno = e.deptno
                    GROUP BY deptno);ENAME||''||JOB DEPTNO SAL
    ALLEN SALESMAN      30     1600
    JONES MANAGER      20     2975
    BLAKE MANAGER      30     2850
    SCOTT ANALYST      20     3000
    KING PRESIDENT      10     5000
    FORD ANALYST      20     3000

  • Correlated Subquery Issue

    the following sample is from ORACLE DATABASE 10g SQL
    i don't understand how it works, the bellow is the table and the query
    SELECT Product_id pid, product_type_id ptid, name, price
    FROM products
    PID PTID NAME PRICE
    1 1 Modern Science 19.95
    2 1 Chemistry 30
    3 2 Supernova 25.99
    4 2 Tank War 13.95
    5 2 Z Files 49.99
    6 2 2412: The Return 14.95
    7 3 Space Force 9 13.49
    8 3 From Another Planet 12.99
    9 4 Classical Music 10.99
    10 4 Pop 3 15.99
    11 4 Creative Yell 14.99
    PID PTID NAME PRICE
    12 My Front Line 13.49
    the query
    SELECT product_id pid, product_type_id ptid, name, price
    FROM products outer
    WHERE price >
    (SELECT AVG(price)
    FROM products inner
    WHERE inner.product_type_id = outer.product_type_id)
    PID PTID NAME PRICE
    2 1 Chemistry 30
    5 2 Z Files 49.99
    7 3 Space Force 9 13.49
    10 4 Pop 3 15.99
    11 4 Creative Yell 14.99
    what i don't understand is HOW and WHEN the AVG function works and HOW AVG() function knows to calculate the average by grouping the PTID not the average of ALL PRICE column.
    tks for helping in advance

    The subquery
    (SELECT AVG(price)
       FROM products inner
      WHERE inner.product_type_id = outer.product_type_id)knows to create an average of all the products with the same product type because of the WHERE clause, which limits the rows returned to those with the product_type_id in the outer.
    Conceptually, what happens is
    - the outer query gets the first row of the table (PID=1)
    - it grabs the price (19.95)
    - now, it runs the subquery to determine whether this is above average
    - the subquery sees that outer.product_type_id is 1, so the WHERE clause eliminates all but the first two rows (PID 1&2). The average of 19.95 and 30 is 24.975.
    - Since the price of the first row is not greater than 24.975, Oracle knows that it does not meet the conditions of the WHERE clause in the outer query.
    - Repeat for each row in the outer query
    Obviously, since Oracle is doing set-based processing, it may not work exactly this way internally. Conceptually, though, this is how correlated subqueries work.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Nested Correlated Subquery

    Hi All,
    I have a SQL query that I am looking to amend. The query currently shows routes from an A end location and a Z end location. On those routes, orders are placed. I have been asked to show only the routes that have more than one order on them. For this I have written the following subquery in the WHERE clause...
    AND    (
            SELECT COUNT(*) qty
            FROM (
                SELECT *
                FROM SCHEMA.ROUTE R
                WHERE r.a_order_id = 457044
                UNION
                SELECT *
                FROM SCHEMA.ROUTE R
                WHERE r.z_order_id = 457044)
                                                            ) > 1Due to the nature of the data, the UNION is needed to ensure orders that are built on either the A or the Z ends are counted.
    The problem here is that I would like to use the a_order_id and z_order_id from the parent query to feed the '457044' values in the subquery. As I'm sure you're all aware, Oracle will only let you use the parent query values one level deep.
    Can anyone see a way of doing this? I can't seem to see the wood through the trees on this one. Any help greatly appreciated.
    Thanks,
    Kev
    Edited by: kevino17 on 21-Nov-2012 03:23

    Hi, Kev,
    Welcome to the forum!
    kevino17 wrote:
    Hi All,
    I have a SQL query that I am looking to amend. The query currently shows routes from an A end location and a Z end location. On those routes, orders are placed. I have been asked to show only the routes that have more than one order on them. For this I have written the following subquery in the WHERE clause...
    AND    (
    SELECT COUNT(*) qty
    FROM (
    SELECT *
    FROM SCHEMA.ROUTE R
    WHERE r.a_order_id = 457044
    UNION
    SELECT *
    FROM SCHEMA.ROUTE R
    WHERE r.z_order_id = 457044)
    ) > 1Due to the nature of the data, the UNION is needed to ensure orders that are built on either the A or the Z ends are counted.It's unclear why you need a UNION. Why not
        SELECT  COUNT (*)
        FROM    schema.route  r
        WHERE   s.order_id  IN (r.a_order_id, r.z_order_id)
    )where s.order_id is a value (such as 457044) from the super-query?
    Whenever you have a question, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) for all the tables involved, and the results you want from that data, so that the people who want to help you can re-create the problem and test their ideas.
    Explain, using specific examples, how you get those results from that data.
    Always say what version of Oracle you're using (e.g. 11.2.0.2.0).
    See the forum FAQ {message:id=9360002}

  • Correlated Subquery in ORDER BY

    The following is a valid sql. But, what is meant by a correlated scalar subquery in the ORDER BY clause?
    SELECT employee_id, last_name
    FROM employees e
    ORDER BY (SELECT department_name
    FROM departments d
    WHERE e.department_id=d.department_id);

    It is exactly the same in the ORDER BY clause as in any other part of a query. As biswabijay says, the correlated query is run once for each row in the result set.
    In essence, the fileds selected from the correlated query are added to the result for each row, then evaluated in the appropriate context (e.g. compared in a WHERE clause, used for sorting in an ORDER BY).
    A small addition to your original query makes this more apparent.
    SQL> SELECT employee_id, last_name, department_name
      2  FROM employees e, departments d
      3  WHERE e.department_id=d.department_id
      4  ORDER BY (SELECT department_name
      5  FROM departments d
      6  WHERE e.department_id=d.department_id);
    EMPLOYEE_ID LAST_NAME                 DEPARTMENT_NAME
            205 Higgins                   Accounting
            206 Gietz                     Accounting
            200 Whalen                    Administration
            100 King                      Executive
            101 Kochhar                   Executive
            102 De Haan                   Executive
            185 Bull                      Shipping
            144 Vargas                    Shipping
            143 Matos                     Shipping
            184 Sarchand                  ShippingHTH
    John

  • Correleated subquery

    Hi folks,
    I have a requirement. I feel i can get it thru correlated sub queries. But am not able to write the complete query. Please help me out on this. Here is the sample data.
    SEQ     VERSION     PARENT_SEQ     CHILD_SEQ
    959     0          976
    976     1     959     1,077
    1,077     2     976     1,079
    1,079     3     1,077     
    In this requirement. User will give any one of the seq number in the family.. I should get the whole family of that seq no. I mean both parents and childs. And also i should be able to inform what is the base parent for all the records. I mean version 0 seq number.
    Please help me out ASAP..
    Thanks in advance.

    Thank you. I got it.
    I used the below query
    (select a.LCSEQ,a.LC_NUMBER, a.LC_VERSION,a.PARENT_LCSEQ, a.CHILD_LCSEQ
    from lcgc.lc_trans a
    start with a.LCSEQ = 976
    CONNECT BY a.LCSEQ = prior a.parent_lcseq)
    union
    (select LCSEQ,LC_NUMBER, LC_VERSION,PARENT_LCSEQ, CHILD_LCSEQ
    from lcgc.lc_trans
    start with LCSEQ = 976
    CONNECT BY prior lcseq = parent_lcseq)

  • Correlated subquery alternatives?

    Before I start, this is a production system and I am not allowed to alter ANY of the tables involved: so no new columns are allowed, tables can't be changed into being materialized views, and no I can't just re-design the entire application that I've inherited! The ONLY thing I can do is change the SQL code used to perform assorted tasks. The tables involved have all got fresh statistics computed, too, so this isn't a question about improving my DBA techniques. Nor is it a question about tuning the performance of existing code (which already has good execution plans).
    I have a large table, called SEARCH. It is a copy of a lot of data from a table called SOURCE (not all of the data, because some is filtered out). SOURCE has about 7 million rows. SEARCH has about 5 million. From time to time, records in SOURCE have their status changed from ACTIVE to INACTIVE. If they are marked INACTIVE, they are not allowed to be in SEARCH. Weekly, we re-synch the SEARCH data with the SOURCE -so, it's during that weekend refresh operation that this sort of query is issued:
    delete from SEARCH where IDENTIFIER in (select IDENTIFIER from SOURCE where STATUSCODE != 1);It's a delete using a standard correlated sub-query. It takes slightly over five minutes to run, which is OK, but I would like to know if there's any alternative SQL or SQL constructs/features/enhancements which could be used to perform the same sort of thing more quickly. As I say, I'm not asking how to tune this sort of thing: I'm asking rather if there are alternatives to it. If there isn't, that's OK.
    I should perhaps add that the STATUSCODE column is not found in the SEARCH table (because if the record's in SEARCH, it would be because the status was =1 in SOURCE originally)

    I tried very hard to prevent this sort of post, but clearly I have not succeeded.
    The question actually asked whether there were SQL constructs which could act as an alternative to a correlated sub-query. I see two people have been able to supply such alternatives.
    Those people did not need to double-think what 'active' and 'inactive' meant, or whether the value stored in the statuscode column was 'active' or '1' (I expect they were smart enough to work out that a "status" of active can be encoded in a column called "statuscode" with a value of '1')
    Those people did not read the words "I can't alter any of the tables" and then decide to ignore them as you have (creating an index on a table counts as altering the table in my book and in this context)
    Those people did not read the words 'fresh statistics have been computed' and decide to suggest calculating even fresher statistics that include histograms.
    Those people did not need to start guessing what my data distribution for inactive records is.
    Those people did not read the words "[This is not] a question about tuning the performance of existing code (which already has good execution plans)" and ignore them, deciding in their arrogance that maybe those execution plans needed to be discussed after all.
    Why can't you and others like you just stick to answering the question as asked for once? Two other people in this exchange have managed to do just that, yet so many of these 'thousands of posts to my name' frequenters of these forums seem completely incapable of doing so. It is very strange, very frustrating and I wish you wouldn't do it.

  • How to INSERT into table using CORRELATED subquery

    I have 3 tables:
    1.TEMP_PHONE(person_id, phonenumber, phone_type) - this holds all phone numbers relating to a person(just a temporary holding area)
    2.PHONE_CONNECT(PERSON_ID, PHONE_ID) this table shows all the phone numbers relating to an individual. Phone_id is a unique number to identify a phonenumber and type(cell, work, home) - so in this table a person can have multiple phone ids)
    3.MASTER_PHONE(PHONE_ID, PHONENUMBER, PHONE_TYPE) this is a master phone table. each combination of phone number and type has a unique identifier-phone_id.
    What i need to figure out is how to populate PHONE_CONNECT with the information from TEMP_PHONE IF PERSON_ID already exists but phone_id is different. In other words, if the person gets a new phone number, i need to insert a new row into phone_connect.
    Before that step is started, the master_phone is populated first with a new phone_id associated to the phonenumber/type
    any help would be much appreciated. Thanks in advance.
    So far, this is what i have come up with, but not sure if it makes sense:
    insert into phone_connect(person_id)
    select a.person_id
    from temp_phone a
    where
    person_id = (select b.person_id from phone_connect b, master_phone c
    where
    a.person_id=b.person_id
    and b.phone_id <> c.phone_id
    and c.phonenumber||c.phone_type=a.phonenumber||a.phone_type);
    update phone_connect c
    set phone_id=(
    select b.phone_id
    from temp_phone a, master_phone b
    where a.person_id = c.person_id
    and a.phonenumber||a.phone_type = b.phonenumber||b.phone_type)
    where phone_id is null;

    It does. You are right. But that's what i need help with. I don't think my code is correct. After the insert, the code is actually updating the same exact record I just inserted. I'm sure this all can be done with one insert. I just really don't know how to show that in my code.
    I need to insert a new record into phone_connect with person_id and phone_id. phone_id is already populated in master_phone. I guess my problem is how to go about creating the joins to all three tables to make sure im inserting the data correctly, or not inserting data that already exists.

Maybe you are looking for