[
https://jira.jboss.org/jira/browse/JBIDE-4486?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4486:
----------------------------------------
There are 2 workarounds:
1. Implement custom ReverseEngineeringStrategy's method and use the strategy
public String getTableIdentifierStrategyName(TableIdentifier tableIdentifier) {
return "identity";
}
Subclass DefaultReverseEngineeringStrategy for this.
2. Implement custom HSQLMetaDataDialect (subclass JDBCMetaDataDialect):
public Iterator getSuggestedPrimaryKeyStrategyName(String catalog,
String schema, String table) {
...
m.put( "HIBERNATE_STRATEGY", "identity" );
...
}
Include it into configuration by
<property
name="hibernatetool.metadatadialect">fix.HSQLMetaDataDialect</property>
Primary Key or Idenity not being respected
------------------------------------------
Key: JBIDE-4486
URL:
https://jira.jboss.org/jira/browse/JBIDE-4486
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.0.0.GA
Environment: Fedora 10 JDK 5
Reporter: Jim Tyrrell
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.1.0.CR2
When reverse engineering either a MySQL or a HSQLDB, the auto numbered identity fields
are not being respected creating issues in the Web UI ie a number is being asked for
(better select a valid one), and the generated Entity Bean does not have a @GeneratedValue
in it. This happens when selected Seam 2.0 in the first page of the wizard.
--
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