Bug 111731 - Attribute / association cardinality in PDL should be compulsory
Attribute / association cardinality in PDL should be compulsory
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
Depends On:
  Show dependency treegraph
Reported: 2003-12-09 09:12 EST by Daniel Berrange
Modified: 2007-04-18 13:00 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-02 13:30:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2003-12-09 09:12:00 EST
Description of problem:
The lack of cardinality definitions (ie [0..1], [1..1], etc) for
attributes has been a major source of unexpected problems & bugs in
both object type & query definitions. There is no reason aside from
laziness why an application developer should not explicitly define the
cardinality for all query & object type attributes. The PDL parser
should be changed to make cardinality compulsory. Any object types
without this information can be trivially fixed up by either
mechanically adding '[0..1]' (to preserve current default behaviour)
or examining the domain code to determine the precise requirements.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:
Error is thrown when an object typee / query attribute does not define
its cardinality.

Additional info:
Comment 1 Daniel Berrange 2006-09-02 13:30:30 EDT
Closing old tickets

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