[
https://issues.apache.org/jira/browse/OFBIZ-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797322#comment-13797322
]
Christian Carlow commented on OFBIZ-5356:
-----------------------------------------
I don't mean to "open a can of worms" because I realize the amount of work that
would be entailed, but wouldn't having single field primary keys for all tables
be better database design? It would definitely allow for the unique record
selection of any Lookup entity list.
> Ability to select Lookup records having more than one primary key field
> -----------------------------------------------------------------------
>
> Key: OFBIZ-5356
> URL: https://issues.apache.org/jira/browse/OFBIZ-5356
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Release Branch 12.04
> Reporter: Christian Carlow
>
> Having the ability to select a record from Lookup records containing more
> than one primary-key field would be quite useful.
> I have the need to select a single OrderItem from a list of OrderItems
> associated with more than one OrderHeader. I also need to be able to select
> a single ShipmentItem from a list containing multiple Shipments.
> Having single field primary keys for these tables would provide a solution
> but would entail a lot of work to make the system use the new primary keys.
> Another way would be to allow for Lookup controls the ability to have
> multiple keys associated with them.
> Either way, seems like a lot of work to make this happen.
> Anyone have a different solution?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
