X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B9B39D1B4F1 for ; Tue, 11 Nov 2003 16:32:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 74211-06 for ; Tue, 11 Nov 2003 12:32:23 -0400 (AST) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by svr1.postgresql.org (Postfix) with ESMTP id 1BEA5D1B509 for ; Tue, 11 Nov 2003 12:32:22 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.12.9p2/8.12.9) with ESMTP id hABGW6RY097838; Tue, 11 Nov 2003 17:32:06 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Tue, 11 Nov 2003 17:32:06 +0100 From: Palle Girgensohn To: Tom Lane Cc: pgsql-sql@postgresql.org Subject: Re: curly braces to group outer joins in queries from Message-ID: <43580000.1068568326@rambutan.pingpong.net> In-Reply-To: <6997.1068568137@sss.pgh.pa.us> References: <24750000.1068552259@rambutan.pingpong.net> <111.1068561592@sss.pgh.pa.us> <40060000.1068567321@rambutan.pingpong.net> <6997.1068568137@sss.pgh.pa.us> X-Mailer: Mulberry/3.0.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/121 X-Sequence-Number: 15936 Only, I set up postgreql to connect using JDBC... :( So, the bug is that OO expects an ODBC connection, and I use JDBC... Seems logical. I'll go ask the ODBC guys. Thanks for you help, /Palle --On tisdag, november 11, 2003 11.28.57 -0500 Tom Lane wrote: > Palle Girgensohn writes: >> Here's their code snippet (from >> oo_1.1_src/dbaccess/source/ui/querydesign/QueryDesignView.cxx): > >> if(aJoin.getLength()) >> { >> ::rtl::OUString aStr = ::rtl::OUString::createFromAscii("{ OJ "); >> aStr += aJoin; >> aStr += ::rtl::OUString::createFromAscii(" },"); >> aTableListStr += aStr; >> } > > Now that I look at it, I bet that they are expecting the ODBC driver to > translate "{ OJ ... }" into the appropriate syntax for the database > (either SQL standard or not, depending on the DB :-(). > > There are a number of ODBC brace-constructs that our driver knows how to > translate, but I don't think that's one of them. You should bug the > ODBC guys about it. > > regards, tom lane