And, ftr, you need to create a view for Remedy to be able to lay a view form over it. If you don't need the view form, there are other options. Since you didn't say what the usage of the data is I am not sure we can recommend any other options that might be more efficient or useful.
On Wed, Jul 23, 2008 at 2:19 PM, Grooms, Frederick W < [EMAIL PROTECTED]> wrote: > ** You gave him the select statement for a view > > A view would be something like > > Create or Replace VIEW My_View_Name > (TABLEA_COL1, TABLEA_COL2, TABLEA_COL3, TABLEA_COL4, TABLEB_COL1, > TABLEB_COL2, TABLEB_COL3, TABLEB_COL4) > as > ( > SELECT TABLEA.COL1, TABLEA.COL2, TABLEA.COL3, TABLEA.COL4, TABLEB.COL1, > TABLEB.COL2, TABLEB.COL3, TABLEB.COL4 > FROM TABLEA LEFT JOIN TABLEB ON TABLEA.COL1 = TABLEB.COL1 > UNION > SELECT TABLEA.COL1, TABLEA.COL2, TABLEA.COL3, TABLEA.COL4, TABLEB.COL1, > TABLEB.COL2, TABLEB.COL3, TABLEB.COL4 > FROM TABLEB LEFT JOIN TABLEA ON TABLEA.COL1 = TABLEB.COL1 > ) > Fred > > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Kemes, Lisa > *Sent:* Wednesday, July 23, 2008 2:46 PM > > *To:* [email protected] > *Subject:* Re: Full Outer Joins? > > I talked to my DB guy about the View on the DB and he is telling me that > it's not really a view. Here's what I gave him: > > > SELECT TABLEA.COL1, TABLEA.COL2, TABLEA.COL3, TABLEA.COL4, TABLEB.COL1, > TABLEB.COL2, TABLEB.COL3, TABLEB.COL4 > > FROM TABLEA LEFT JOIN TABLEB ON TABLEA.COL1 = TABLEB.COL1 > > UNION > > SELECT TABLEA.COL1, TABLEA.COL2, TABLEA.COL3, TABLEA.COL4, TABLEB.COL1, > TABLEB.COL2, TABLEB.COL3, TABLEB.COL4 > > FROM TABLEB LEFT JOIN TABLEA ON TABLEA.COL1 = TABLEB.COL1 > > > > He said he is going to look into this further, but I think it's a view > right? > > Lisa > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Brian Goralczyk > *Sent:* Wednesday, July 23, 2008 2:56 PM > *To:* [email protected] > *Subject:* Re: Full Outer Joins? > > ** There is always the option to create a join view in the database and > throwing a view form on top of that. It would allow you to perform database > functions that Remedy just won't do. > > HTH, > > Brian > > On Wed, Jul 23, 2008 at 12:44 PM, Janie <[EMAIL PROTECTED]> wrote: >> >> OOB Joins are Left Outer from Parent to Child forms. Not Full >> Left/Right Outer…. >> >> Someone else may have additional thoughts on how to simulate a Full Outer >> join within the confines of AR System joins, but as far as I know what you >> are trying to do may have to be rethought for a different approach…. >> >> Janie >> ------------------------------ >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Kemes, Lisa >> *Sent:* Wednesday, July 23, 2008 9:43 AM >> *To:* [email protected] >> *Subject:* Full Outer Joins? >> >> Does AR System support Full Outer Joins on a Join Table? >> >> I need to combine the results of both left and right outer joins. The >> joined table will contain all records from both tables, and fill in NULLs >> for missing matches on either side. >> >> Our environment: >> AR Server 7.0.1 Patch 3 >> MT 7.0.1 Patch 5 >> Oracle 10i >> >> *Lisa Kemes** * >> AR System Developer >> Tyco Electronics >> 717-810-2408 tel >> 717-810-2124 fax >> [EMAIL PROTECTED] >> > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
