This is looking very promising but probably also needs 'niced up'
dictionaries - our collection of randomly generated dicts doesn't cut it
and I'm getting some fields unnesting and some fields as MV lists per
unnested row.
AAAAAA 12345 description of 12345
Description of 9999
Description of 7625
AAAAAA 9999 description of 12345
Description of 9999
Description of 7625
AAAAAA 7625 description of 12345
Description of 9999
Description of 7625
Should I be looking at using @ASSOC_KEY?
>-----Original Message-----
> If so, use an SQL UNNEST keyword, e.g.
> SELECT SURNAME,FORENAME,TITLE_ID,QTY,PRICE FROM UNNEST
>BOOK_SALES ON
> SALE_ITEMS;
>
> You can explode a field to a select list by using the TO SLIST
clause, e.g.
>
> SELECT TITLE_ID TO SLIST 0 FROM UNNEST BOOK_SALES ON SALE_ITEMS;
**********************************************************************
This email message and any files transmitted with it are confidential and
intended solely for the use of addressed recipient(s). If you have received
this communication in error, please reply to this e-mail to notify the sender
of its incorrect delivery and then delete it and your reply. It is your
responsibility to check this email and any attachments for viruses and defects
before opening or sending them on. Spotless collects information about you to
provide and market our services. For information about use, disclosure and
access, see our privacy policy at http://www.spotless.com.au
Please consider our environment before printing this email.
**********************************************************************
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
