Mailing-List: contact commits-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Date: Wed, 4 Feb 2015 02:20:34 +0000 (UTC)
From: "John Huss (JIRA)" <jira@apache.org>
To: commits@cayenne.apache.org
Message-ID: <JIRA.12772190.1423006139000.249681.1423016434542@Atlassian.JIRA>
In-Reply-To: <JIRA.12772190.1423006139000@Atlassian.JIRA>
References: <JIRA.12772190.1423006139000@Atlassian.JIRA>
 <JIRA.12772190.1423006139648@arcas>
Subject: [jira] [Commented] (CAY-1986) SQLTemplate returning DataObjects
 fails on PK column case mismatch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Huss commented on CAY-1986:
--------------------------------

Just ignore case?  It already does for all the other column except the PK.

> SQLTemplate returning DataObjects fails on PK column case mismatch
> ------------------------------------------------------------------
>
>                 Key: CAY-1986
>                 URL: https://issues.apache.org/jira/browse/CAY-1986
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 4.0.M2
>         Environment: trunk
>            Reporter: John Huss
>            Priority: Minor
>
> If you create an SQLTemplate query that returns real DataObjects (say Artist objects) and use a query like "select * from Artist limit 1" and have the primary key column defined in the DataMap with mixed case (like artist_ID) that doesn't match what the database returns for the column name, the result will contain nulls instead of objects.
> Strangely the case of the other columns does not seem to matter, only the primary key column.
> You can workaround it by naming the column all upper or lower case and configuring the SQLTemplate to force upper or lower case column names to be returned.  But I think it should just work without needing to do this.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)