Bug 112905 - Multiple object types using same physical table -> incorrect constraints
Summary: Multiple object types using same physical table -> incorrect constraints
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: persistence
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 111730
TreeView+ depends on / blocked
 
Reported: 2004-01-05 19:20 UTC by Richard Li
Modified: 2020-03-27 16:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 16:49:33 UTC
Embargoed:

Attachments (Terms of Use)

Description Richard Li 2004-01-05 19:20:36 UTC 
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.