Bug 112905 - Multiple object types using same physical table -> incorrect constraints
Multiple object types using same physical table -> incorrect constraints
Status: NEW
Product: Red Hat Web Application Framework
Classification: Retired
Component: persistence (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks: 111730
  Show dependency treegraph
 
Reported: 2004-01-05 14:20 EST by Richard Li
Modified: 2008-05-01 11:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Richard Li 2004-01-05 14:20:36 EST
When multiple object types are using the same physical data model,
incorrect constraints can be generated.

Suppose B extends A. If you specify a property in B that maps into the
physical table that stores A, and you specify that property as 1..1,
then the a not null constraint is generated on that property for the
data model, when in fact this constraint should be enforced by
persistence.

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