Bug 112905

Summary:	Multiple object types using same physical table -> incorrect constraints
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Richard Li <richardl>
Component:	persistence	Assignee:	ccm-bugs-list
Status:	CLOSED EOL	QA Contact:	Jon Orris <jorris>
Severity:	medium	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:	2020-03-27 16:49:33 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:
Bug Blocks:	111730

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.