We know that's the CURRENT fundamental design... We're talking an extension to that design for those who would find it useful. I never use many parts of UniData - should those be removed because I don't see the need? <g>
The issue is that UniData (where we all are) does NOT have a PartFile. If we had PartFiles, that would address exactly the issue we speak of - the ability to segregate data but retrieve it as one logical file. Adding PartFiles to UniData would remove the need for a multi-file SELECT/LIST (MSELECT and MLIST?) -- Which would be easier to implement by IBM? David W. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Schasny > Sent: Wednesday, May 16, 2007 12:21 PM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] [UD] Union Query > > I vote no. The UV/UD query language is fundamentally designed > to work against one file with correlatives/I-types pointing > to any other tables from which we require related data. This > is something at the core of our environment. The problem here > is, shall we say, problematic database design. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
