Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


drew jensen wrote:
On Fri, 2012-07-20 at 09:51 -0400, Dan wrote:
The outline for the FROM clause for a LEFT OUTER JOIN is

FROM “table1 name” LEFT OUTER JOIN “table2 name” ON “table1
name”.”foreign key” = “table2 name”.”primary key”

       This is what I entered into a query yesterday. Yet, today when I
edited the query in SQL view I saw

FROM { OJ "Persons" LEFT OUTER JOIN "Orders" ON "Persons"."P_ID" =
"Orders"."P_ID" }

       Braces and OJ were added. This is using LO 3.5.5.3. I got a
similar result when using SQL to create a RIGHT OUTER JOIN. Does anyone
know where this is documented? It appears Base is adding this for
clarity. Should this be included this in the documentation?


Hi Dan

The use of ODBC conventions, '{ OF' for example, is controlled with an
option on the ODB file.

Open the ODB.
Open the dialog for options:
Edit>Database>Advanced Options

//drew
     Thanks!

Is it a good idea to have the three conventions checked that are listed there? Why or why not?

--Dan

--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.