Red Hat Bugzilla – Bug 478011
MIGRATED_FROM_JIRA: Need interface to set source primary keys
Last modified: 2015-01-04 18:35:30 EST
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.
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.
Closing bug as it was already closed in Jira - PENROSE-1