Bug 478011

Summary: MIGRATED_FROM_JIRA: Need interface to set source primary keys
Product: [Retired] penrose Reporter: Chandrasekar Kannan <ckannan>
Component: StudioAssignee: Endi Sukma Dewata <edewata>
Status: CLOSED UPSTREAM QA Contact: Chandrasekar Kannan <ckannan>
Severity: low Docs Contact:
Priority: low    
Version: 2.0CC: asaf, benl, nmalki, sramling
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: 2008-12-27 07:31:55 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: 471500    

Description Chandrasekar Kannan 2008-12-27 07:31:53 UTC 
Current problem:

When adding a new source from a JDBC connection, the mapping tool relies on information from the database schema to determine the primary keys for that source. This is not right since user may want to use different fields for mapping purposes.

When adding a new source from a JNDI connection, the mapping tool does not assign any primary keys at all. This is not right since the primary keys are needed to construct the rdn on update operations.

Proposed solution:

We need to have a way to select/modify which fields will be used as the primary keys of a particular source.

Additional Comments From adison dated Mon Apr 18 15:28:06 CDT 2005 
Resolved this issue for the JNDI source.
Currently JDBC source still  relies on database metadata for the primary key information for a particular field.
Comment 1 Chandrasekar Kannan 2008-12-27 07:31:55 UTC 
Closing bug as it was already closed in Jira - PENROSE-1