I had not thought of the index, but it does show up in the EXPLAIN data. >>.X 01 LIST SA SLSMLINELOCCAT.IDX WITH SLSMLINELOCCAT.IDX = "[KK]" AND WITH CUSTLINELOCCAT.IDX = "[LL]" EXPLAIN Single-variable predicates processed in index: F0 MATCHES '...'KK'...' AND F0 MATCHES '...'LL'...' Optimizing query block 0
Driver source: SA Access method: select list 0 with 0 ids UniVerse/SQL: Press any key to continue or 'Q' to quit Obviously a PICK flavor UniVerse 10.1.11, AIX 5.3.2 Tom Dodds [EMAIL PROTECTED] 708-234-9608 Office 630-235-2975 Cell -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laura Hirsh Sent: Friday, October 13, 2006 2:22 PM To: [email protected] Subject: RE: [U2] Sort / Select keyword Interesting. I was just thinking that something similar would be useful - especially when using indexes and being able to tell if an index is being used or not. Anyone know of anything similar in Unidata? Thanks, Laura -----Original Message----- >From: Tom Dodds <[EMAIL PROTECTED]> >Sent: Oct 13, 2006 12:40 PM >To: [email protected] >Subject: RE: [U2] Sort / Select keyword > >This is what I got using EXPLAIN on UV 10.1.11 under AIX 5.3 > >LIST P/O ORDER CUST P/O-DATE BY CUST WITH CUST > "1" EXPLAIN >Optimizing query block 0 >Tuple restriction: F3 > '1' > >Driver source: P/O >Access method: file scan > >Sorted by: CUST >UniVerse/SQL: Press any key to continue or 'Q' to quit ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
