You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2012/11/01 22:56:12 UTC

[jira] [Created] (CAY-1755) FaultFailureException resolving relationships to UNIQUE non-PK columns

Andrus Adamchik created CAY-1755:
------------------------------------

             Summary: FaultFailureException resolving relationships to UNIQUE non-PK columns
                 Key: CAY-1755
                 URL: https://issues.apache.org/jira/browse/CAY-1755
             Project: Cayenne
          Issue Type: Bug
          Components: Core Library
    Affects Versions: 3.1B1, 3.0.2, 3.2M1
            Reporter: Andrus Adamchik
            Assignee: Andrus Adamchik
             Fix For: 3.1B2, 3.2M1


This was discussed under CAY-1751. When a relationship to UNIQUE non-PK column (the column is marked as a second PK column as a workaround) is read, FFE is thrown. The problem is that the object with an FK incorrectly assumes that it can build a target object ObjectId based on the FK. This totally disregards the second PK column not participating in relationship.

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

[jira] [Closed] (CAY-1755) FaultFailureException resolving relationships to UNIQUE non-PK columns

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAY-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik closed CAY-1755.
--------------------------------

    Resolution: Fixed
    
> FaultFailureException resolving relationships to UNIQUE non-PK columns
> ----------------------------------------------------------------------
>
>                 Key: CAY-1755
>                 URL: https://issues.apache.org/jira/browse/CAY-1755
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0.2, 3.1B1, 3.2M1
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1B2, 3.2M1
>
>         Attachments: cay1751.tar.gz
>
>
> This was discussed under CAY-1751. When a relationship to UNIQUE non-PK column (the column is marked as a second PK column as a workaround) is read, FFE is thrown. The problem is that the object with an FK incorrectly assumes that it can build a target object ObjectId based on the FK. This totally disregards the second PK column not participating in relationship.

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

[jira] [Updated] (CAY-1755) FaultFailureException resolving relationships to UNIQUE non-PK columns

Posted by "Andrus Adamchik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAY-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik updated CAY-1755:
---------------------------------

    Attachment: cay1751.tar.gz

attaching a full git project with the mapping and the tests
                
> FaultFailureException resolving relationships to UNIQUE non-PK columns
> ----------------------------------------------------------------------
>
>                 Key: CAY-1755
>                 URL: https://issues.apache.org/jira/browse/CAY-1755
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0.2, 3.1B1, 3.2M1
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.1B2, 3.2M1
>
>         Attachments: cay1751.tar.gz
>
>
> This was discussed under CAY-1751. When a relationship to UNIQUE non-PK column (the column is marked as a second PK column as a workaround) is read, FFE is thrown. The problem is that the object with an FK incorrectly assumes that it can build a target object ObjectId based on the FK. This totally disregards the second PK column not participating in relationship.

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