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
