Databases
StackOverflow2013
Postsdbo
POIs there an alternative to the MULTISET operator that avoids sub-queries?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there an alternative to the MULTISET operator that avoids sub-queries?
    primarykey
    data
    text
    <p>Suppose you have a table as follows:</p> <pre><code>CREATE TABLE EMPLOYEE_SALES ( EMPLOYEE_ID NUMBER, PRODUCT_ID NUMBER, SALE_AMOUNT NUMBER ); </code></pre> <p>And suppose it is populated as follows:</p> <pre> +-------------+------------+-------------+ | EMPLOYEE_ID | PRODUCT_ID | SALE_AMOUNT | +-------------+------------+-------------+ | 1 | 100 | 1.05 | | 1 | 200 | 45.67 | | 2 | 100 | 3.25 | | 2 | 200 | 34.29 | +-------------+------------+-------------+ </pre> <p>Now, suppose I create a custom type named <code>SALE_TYPE</code> which represents a <code>(PRODUCT_ID, SALE_AMOUNT)</code> tuple:</p> <pre><code>CREATE TYPE SALE_TYPE IS OBJECT ( PRODUCT_ID NUMBER, SALE_AMOUNT NUMBER ); </code></pre> <p>And suppose I also create a custom type named <code>SALES_TYPE</code> which represents a <code>TABLE</code> of <code>SALE_TYPE</code>:</p> <pre><code>CREATE TYPE SALES_TYPE IS TABLE OF SALE_TYPE; </code></pre> <p>I want to query the <code>EMPLOYEE_SALES</code> table group by <code>EMPLOYEE_ID</code>. For each <code>EMPLOYEE_ID</code>, I wish to create a <code>SALES_TYPE</code> containing that employee's sales. According to the documentation, I would do something like this:</p> <pre><code>SELECT EMPLOYEE_ID, CAST ( MULTISET ( SELECT PRODUCT_ID, SALE_AMOUNT FROM EMPLOYEE_SALES inner_employee_sales WHERE inner_employee_sales.employee_id = employee_sales.employee_id ) AS SALES_TYPE ) AS SALES FROM EMPLOYEE_SALES GROUP BY EMPLOYEE_ID </code></pre> <p>I expect this query to yield something like this:</p> <pre> +-------------+------------------------------+ | EMPLOYEE_ID | SALES | +-------------+------------------------------+ | 1 | +------------+-------------+ | | | | PRODUCT_ID | SALE_AMOUNT | | | | +------------+-------------+ | | | | 100 | 1.05 | | | | | 200 | 45.67 | | | | +------------+-------------+ | +-------------+------------------------------+ | 2 | +------------+-------------+ | | | | PRODUCT_ID | SALE_AMOUNT | | | | +------------+-------------+ | | | | 100 | 3.25 | | | | | 200 | 34.29 | | | | +------------+-------------+ | +-------------+------------------------------+ </pre> <p>Is there a way to achieve the same results without issuing a sub-query (the <em>real</em> query I am working on is much more complicated than this contrived example)? For example, is there something like this:</p> <pre><code>SELECT EMPLOYEE_ID, CAST ( COLLECT_ALL_RECORDS_WITHIN_THE_CURRENT_GROUP( PRODUCT_ID, SALE_AMOUNT ) AS SALES_TYPE ) AS SALES FROM EMPLOYEE_SALES GROUP BY EMPLOYEE_ID </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAdam Paynter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs there an alternative to the MULTISET operator that avoids sub-queries?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs there an alternative to the MULTISET operator that avoids sub-queries?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs there an alternative to the MULTISET operator that avoids sub-queries?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload