You can always create a temporary view on the fly for nested views. I do this sometimes for specific reports using specific clauses and I don't have to worry about the order of views. Once the report is generated, the views is dropped, or if you don't, it goes away when you disconnect.
Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James Bentley Sent: Wednesday, October 30, 2013 11:37 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Left Outer Join However if nested JOIN syntax is used then there is no need to worry about unload order. I got real tired of monitoring view order. I now have 181 views down from a significantly larger number of views when I was using nested views. Jim Bentley, American Celiac Society 1-504-737-3293 -------------------------------------------- On Wed, 10/30/13, Dennis McGrath <[email protected]> wrote: Subject: [RBASE-L] - RE: Left Outer Join To: "RBASE-L Mailing List" <[email protected]> Date: Wednesday, October 30, 2013, 10:57 AM That is why I try to define all related views in one file and run the whole thing when changes are made. I drop all the views in reverse order and recreate them all. Too Bad SYS_VIEWS does not have a SYS_TABLE_LIST colum. Then it would be relatively easy for the unloader to dump nested views in the correct order. Maybe some day. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James Bentley Sent: Wednesday, October 30, 2013 10:39 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Left Outer Join The one disadvantage of using nested views is that if you make a change in any view involved you may need to update all nested views involved. this is especially important if you do UNLOAD/RELOAD since the sequence since RBase maintains an first in first out order for views. Thus for example you create view1, view2, view3 RBase would unload them in that sequence. If you change view1 RBase would unload them in the sequence view2, view3, view1. If view2 and/or view3 used view1 in their WHERE clause the RELOAD of view2 and/or view3 would fail since view1 had not yet been created. The used nested JOINS that do not involve views avoids this problem/ Jim Bentley, American Celiac Society 1-504-737-3293 -------------------------------------------- On Wed, 10/30/13, Dennis McGrath <[email protected]> wrote: Subject: [RBASE-L] - RE: Left Outer Join To: "RBASE-L Mailing List" <[email protected]> Date: Wednesday, October 30, 2013, 10:13 AM The is a new syntax to do multiple outer joins. Personally, I find it very hard to write, read and maintain. I prefer to use nested views to get the job done1 view to do the first outer join1 view using the first view as the left table in the second out join Nothing to keep you from nesting 2 or more views like this to achieve almost anything. Dennis McGrathSoftware DeveloperQMI Security Solutions1661 Glenlake AveItasca IL [email protected]: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Wednesday, October 30, 2013 10:07 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Left Outer Join Trying something new. Can I use 2 left outer joins? Contact is my main table, may or may not be a matching ID in the Client and People table, but I'm getting a syntax error. It works fine with just t1 and t2, errors when I add in the t3 syntax: CREATE VIEW vContactAll AS SELECT t1.*, t2.*, t3.* + FROM Contact t1 + LEFT OUTER JOIN client t2 ON t1.id = t2.id + LEFT OUTER JOIN people t3 ON t1.id = t3.id Karen
