Return-Path: 
 <commits-return-4821-apmail-oodt-commits-archive=oodt.apache.org@oodt.apache.org>
X-Original-To: apmail-oodt-commits-archive@www.apache.org
Delivered-To: apmail-oodt-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2163EDB29
	for <apmail-oodt-commits-archive@www.apache.org>;
 Fri, 21 Dec 2012 00:05:13 +0000 (UTC)
Received: (qmail 26056 invoked by uid 500); 21 Dec 2012 00:05:13 -0000
Delivered-To: apmail-oodt-commits-archive@oodt.apache.org
Received: (qmail 25882 invoked by uid 500); 21 Dec 2012 00:05:12 -0000
Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@oodt.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@oodt.apache.org>
List-Post: <mailto:commits@oodt.apache.org>
List-Id: <commits.oodt.apache.org>
Reply-To: dev@oodt.apache.org
Delivered-To: mailing list commits@oodt.apache.org
Received: (qmail 25867 invoked by uid 99); 21 Dec 2012 00:05:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2012 00:05:12 +0000
Date: Fri, 21 Dec 2012 00:05:12 +0000 (UTC)
From: "Chris A. Mattmann (JIRA)" <jira@apache.org>
To: commits@oodt.apache.org
Message-ID: <JIRA.12624758.1355970759570.39494.1356048312810@arcas>
In-Reply-To: <JIRA.12624758.1355970759570@arcas>
References: <JIRA.12624758.1355970759570@arcas>
Subject: [jira] [Commented] (OODT-546) XMLPS inner-joins default table with
 itself
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/OODT-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537527#comment-13537527 ] 

Chris A. Mattmann commented on OODT-546:
----------------------------------------

Figured this out. Mike in your config, you need to take out the definition of the <table> that is duplicative of the default name in <tables default...>. That fixes the join issue and makes sense. Any <table> definitions inside of the <tables> block are tables that should be "joined" to the default table name by the joinfld and tofld attributes on the <table> tag.
                
> XMLPS inner-joins default table with itself
> -------------------------------------------
>
>                 Key: OODT-546
>                 URL: https://issues.apache.org/jira/browse/OODT-546
>             Project: OODT
>          Issue Type: Bug
>          Components: xmlps
>    Affects Versions: 0.5
>            Reporter: Michael Joyce
>             Fix For: 0.6
>
>         Attachments: dump.sql, ps.xml
>
>
> When the default table is set to an existing table name, XMLPS tries to inner join the default table with itself, resulting in a failed query. 
> Example
> With the following ps.xml file
> {code:xml}
> <oodt:xmlps xmlns:oodt="http://incubator.apache.org/oodt/0.1-incubating"
> 	name="CERC Query Handler" id="EDRN.CERC.CancerData">
> 	<!--<tables default="Table1">-->
>   <tables default="Cancer_Data">
>     <table name="Cancer_Data" join="STUDY_PARTICIPANT_ID_SITE_TEXT" tofld="STUDY_PARTICIPANT_ID_SITE_TEXT"/>
>   </tables>
>   <field type="dynamic" name="STUDY_PARTICIPANT_ID" dbname="STUDY_PARTICIPANT_ID_SITE_TEXT" />
>     
>   <field type="constant" name="BASELINE_CANCER-CONFIRMATION_CODE" value="1"/>
> </oodt:xmlps>
> {code}
> A query to 
> {noformat}
> http://localhost:8080/web-grid/prod?q=RETURN%3DSTUDY_PARTICIPANT_ID
> {noformat}
> Results in the following:
> {noformat}
> WARNING: Error executing sql: [SELECT Cancer_Data.STUDY_PARTICIPANT_ID_SITE_TEXT as STUDY_PARTICIPANT_ID FROM Cancer_Data INNER JOIN Cancer_Data ON Cancer_Data.STUDY_PARTICIPANT_ID_SITE_TEXT = Cancer_Data.STUDY_PARTICIPANT_ID_SITE_TEXT ]: Message: Not unique table/alias: 'Cancer_Data'
> {noformat}
> If the default table is changed to "Participant_Data" then the query functions fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira