Bug 104452

Summary: the join path spec for the second attribute should be optional
Product: [Retired] Red Hat Web Application Framework Reporter: Vadim Nasardinov <vnasardinov>
Component: persistenceAssignee: ccm-bugs-list
Status: CLOSED WONTFIX QA Contact: Jon Orris <jorris>
Severity: low Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-08-03 18:30:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 104451    
Bug Blocks:    

Description Vadim Nasardinov 2003-09-15 20:48:09 UTC
In a two-association definition like this:

association {
   Foo[0..n] foos = join ...

   Bar[0..n] bars = join ...
}

the join path for "bars" can be trivially computed by reversing
the join path specified for "foos".  The PDL compiler can be changed
to support the following syntax:

association {
   Foo[0..n] foos = join ...

   Bar[0..n] bars;
}

The join path for "bars" is omitted and the PDL compiler should
compute it by reversing the join path specified for the "foos"
attribute.  This would reduce the likelyhood of programming errors
by making it unnecessary for the programmer to perform this mechanical
calculation manually.

Comment 1 Vadim Nasardinov 2005-08-03 18:30:14 UTC
stale