Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.0-HEAD, 3.0, 2.0-beta-1, 2.0-beta-2-HEAD, 2.0-beta-2-VALUEOBJECT_REFACTORING_BRANCH
-
Fix Version/s: 3.0-HEAD, 3.0, 2.0-beta-1, 2.0-beta-2-HEAD, 2.0-beta-2-VALUEOBJECT_REFACTORING_BRANCH
-
Component/s: plugin-persistence-adapter
-
Labels:None
-
Number of attachments :
Description
When the chosen key generation scheme needs an extra table (e.g., hilo) and the table entry in the UI is being left empty an error occurs. It would probably be better to not generate the table attribute in the <meta/> element (see below), because in that case Hibernate will use a default name for the necessary table.
<meta attribute="field-description">
@hibernate.id
generator-class="hilo"
type="java.lang.Short"
column="the_table_id"
@hibernate.generator-param
name="table"
value=""
@hibernate.generator-param
name="column"
value="next_value"
@hibernate.generator-param
name="max_lo"
value="100"
</meta>
Also, in that case the column name is "next_hi" instead of "next_value", which may need to be taken into account as well.
Sounds reasonable - see what I can do.