cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Misha Doronin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAY-1484) Flattened attribute queries are incorrectly generated
Date Fri, 24 Sep 2010 21:47:36 GMT

     [ https://issues.apache.org/jira/browse/CAY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Misha Doronin updated CAY-1484:
-------------------------------

    Attachment: bugdemo_maven_derby.zip
                bugdemo_maven_derby_nobug.zip

As you requested, here it goes.
In fact it depends on the order you generate classes in modeler, and in the order dependencies
are placed in BugDemoMap.map.xml
See 
diff -u bugdemo/src/main/resources/BugDemoMap.map.xml bugdemo_nobug/src/main/resources/BugDemoMap.map.xml

And in "bug" configuration, there is commented out line in Main.java, which if enabled, causes
null pointer exception.

> Flattened attribute queries are incorrectly generated
> -----------------------------------------------------
>
>                 Key: CAY-1484
>                 URL: https://issues.apache.org/jira/browse/CAY-1484
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0.1
>         Environment: Gentoo linux
> MySQL 5.1
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
>            Reporter: Misha Doronin
>         Attachments: bugdemo_maven_derby.zip, bugdemo_maven_derby_nobug.zip, CayenneBugDemo.zip
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Attached eclipse project demonstrating issue, including cayenne model
> When creating database structure like:
> table1
>   t1key
>   t1value
>   t2keyref
> table2
>   t2key
>   t2value
>   t3keyref
> table3
>   t3key
>   t3value
> and cayenne model with flattened attribute table3.t3value in table2
> it produces incorrect join query to table2 and 3:
> SELECT t1.t3value, t1.t2key, t0.t2value, t0.t3keyref, t0.t2key FROM testschema.table2
t0 JOIN testschema.table3 t1 ON (t0.t3key = t1.t3keyref) WHERE t0.t2key = ?
> Note t1.t2key, which obviously shouldn't be there and produces error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message