David, I'd vote for that! Here's the language I'd suggest:
SORT, LIST, SELECT, SSELECT (at minimum) should allow for data in multiple data levels as an option. The keyword SPANNING would be used to indicate which data levels or SPANNING ALL for all data levels. When Spanning is used, the @ID will display the source data level and the item ID. Example: SORT DAILY.SUMMARY SPANNING "20070501" "20070502" "20070503" BY-DSND DOLLARS PERSON.ID HAT-SIZES TOTAL DOLLARS BREAK-ON DATA.LEVEL.FROM.ID
- Chuck David Wolverton wrote:
Question for everyone then: Should IBM invent a method to extend the Query languages of UniData/UniVerse to do this 'Temporal File' - a "Cross Data File" SELECT/LIST/SORT?
------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
