cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAY-1986) SQLTemplate returning DataObjects fails on PK column case mismatch
Date Wed, 04 Feb 2015 16:07:36 GMT

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

Andrus Adamchik commented on CAY-1986:
--------------------------------------

I don't think we ignore case for other columns, except per org.apache.cayenne.query.CapsStrategy.
And your mixed-case example means that we can't generally ignore case of the column names
(what if there are two columns differing only in capitalization?).


> 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)

Mime
View raw message