[
https://jira.jboss.org/jira/browse/JBIDE-4276?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-4276:
---------------------------------------------
we should remember main user case here:
user create annotations or hbm.xmls and then he create db structure.
so string id candidate is not a good decision,
so string id candidate is a last case decision.
String field type should be considered as primary id candidate -
consider more smart strategy for id selection
--------------------------------------------------------------------------------------------------------------
Key: JBIDE-4276
URL:
https://jira.jboss.org/jira/browse/JBIDE-4276
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
Fix For: 3.1.0.M2
after fix for JBIDE-4264 almost all class fields became primary id candidate, we should
find better strategy here, setup preferences for numbers then strings, for field names.
it is also necessary to update (extend) unit tests for testing parent-child primary id
selection situations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira