|
Dan, Sounds like the SQL view would be the easiest, then create any additional indexes as usage dictates in the future cheers Colin.W Extension 5800 Direct dial 0870 429 5800 -----Original Message----- From: Dan Bale [mailto:dbale@xxxxxxxxxxxxx] Sent: 17 August 2004 15:11 To: midrange-l@xxxxxxxxxxxx Subject: SQL subquery? sub-something? I come to the SQL well again after not knowing exactly what I'm looking for term-wise. In order to list customers by regional sales manager and have necessary relevant information, I have an SQL that joins four files together, the customer master being the primary table. It works well. Fast as ... heck. Anyway, this SQL result set will be the basis for further information gathering, i.e., sales history, forecasts, etc, for several applications. I would like this "base" SQL to be "invisible", like I envision DDS join logical files where the join logic is defined in the file definition; when I read the file, I don't worry about it being the same join logic in different programs that use it. Whereas, with SQL, if I add the Sales History to the SQL statement, I seem to think there's a risk of introducing a relationship that changes the join logic. I don't know if this makes sense. Don't know if I'm looking at creating an SQL view, then using that in another SQL statement. Or subquery. Or just adding to the existing "base" SQL. I would just like to have an idea of the best way to design it, so that it's flexible for future use. tia, db -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. This e-mail has been sent by a company of Bertram Group Ltd, whose registered office is 1 Broadland Business Park, Norwich, NR7 0WF. This message, and any attachments, are intended solely for the addressee and may contain privileged or confidential information. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender immediately. Opinions, conclusions and statements of intent in this e-mail are those of the sender and will not bind a Bertram Group Ltd company unless confirmed in writing by a director independently of this message. Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.