db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Braeuchi (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OJB-78) setPathOuterJoin() needs clarification
Date Fri, 27 Jan 2006 19:27:37 GMT
     [ http://issues.apache.org/jira/browse/OJB-78?page=all ]
Jakob Braeuchi closed OJB-78:

> setPathOuterJoin() needs clarification
> --------------------------------------
>          Key: OJB-78
>          URL: http://issues.apache.org/jira/browse/OJB-78
>      Project: OJB
>         Type: Improvement
>   Components: PB-API
>     Versions: 1.1 CVS, 1.0.3
>     Reporter: Jakob Braeuchi
>     Assignee: Jakob Braeuchi
>     Priority: Minor
>      Fix For: 1.1 CVS, 1.0.4

> Is setPathOuterJoin() supposed to get a path or a single path component? 
> i.e., if I have an attribute path "activity.staff.firstName" and I want to 
> force an outer join to the "staff" table, should I call 
> setPathOuterJoin("staff") or setPathOuterJoin("activity.staff")?  The name 
> of the method suggests the latter (which I'd think would also be more 
> useful), but the code expects the former: In SqlQueryStatement.java:1069 
> (in, which is the latest on the 1.0 branch), it's checking 
> against ObjectReferenceDescriptor.getAttributeName(), which is just 
> "staff".
> It would seem much more useful to use the full path (in SqlQueryStatement, 
> this would mean testing attrPath rather than attr) - what if I have two 
> different paths to reach the "staff" object and I want inner joins along 
> one path and outer along the other?
> Probably either the method name should be changed to 
> setAttributeOuterJoin() or the implementation should be changed to accept 
> a path.
> -steve

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message