Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C91409FB9 for ; Tue, 7 Feb 2012 16:10:03 +0000 (UTC) Received: (qmail 7107 invoked by uid 500); 7 Feb 2012 16:10:03 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 6928 invoked by uid 500); 7 Feb 2012 16:10:02 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 6916 invoked by uid 99); 7 Feb 2012 16:10:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2012 16:10:02 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2012 16:09:55 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Runbq-0008It-E4 for derby-user@db.apache.org; Tue, 07 Feb 2012 08:09:35 -0800 Message-ID: <33279676.post@talk.nabble.com> Date: Tue, 7 Feb 2012 08:09:34 -0800 (PST) From: TXVanguard To: derby-user@db.apache.org Subject: Re: Porting to standard SQL In-Reply-To: <4F312FE1.4080403@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: brett.denner@lmco.com References: <33253800.post@talk.nabble.com> <4F2B3A91.5090905@gmail.com> <33272288.post@talk.nabble.com> <4F30015B.1000702@oracle.com> <33273439.post@talk.nabble.com> <4F30227C.3030603@oracle.com> <33274358.post@talk.nabble.com> <4F303C84.2050605@oracle.com> <4F303D65.1060803@oracle.com> <33275262.post@talk.nabble.com> <4F312FE1.4080403@oracle.com> X-Virus-Checked: Checked by ClamAV on apache.org Rick, I've discovered a few more wrinkles in some of the UPDATE/INNER JOIN states I have to port. Here's an example: UPDATE T1 INNER JOIN (T2a INNER JOIN T2b ON T2a.B = T2b.B) ON T1.B = T2b.B SET T2a.D = true WHERE (T2b.E=true AND NOT (T1.F=2 AND (T2b.G=2 OR T2b.G=1))); Note that the "table" on the right of the first INNER JOIN is not a table, rather the result of another INNER JOIN. Is there any way to rewrite this in standard SQL? -- View this message in context: http://old.nabble.com/Porting-to-standard-SQL-tp33253800p33279676.html Sent from the Apache Derby Users mailing list archive at Nabble.com.