Bug 104452 - the join path spec for the second attribute should be optional
the join path spec for the second attribute should be optional
Status: CLOSED WONTFIX
Product: Red Hat Web Application Framework
Classification: Retired
Component: persistence (Show other bugs)
nightly
All Linux
medium Severity low
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On: 104451
Blocks:
  Show dependency treegraph
 
Reported: 2003-09-15 16:48 EDT by Vadim Nasardinov
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-03 14:30:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vadim Nasardinov 2003-09-15 16:48:09 EDT
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 14:30:14 EDT
stale

Note You need to log in before you can comment on or make changes to this bug.