Hi all,

Hibernate version:
3.0.5

Mapping documents:
.....
<list
name="lesQuotDetails"
lazy="true"
inverse="false"
cascade="all-delete-orphan"
>
<key column="QUOT_SEQ" not-null="true"/>
<list-index column="LINE_SEQ" base="1"/>
<one-to-many
class="LesQuotDetail"
/>
</list>
.....

Name and version of the database you are using:
Oracle 9


In this case, Hibernate will issue an INSERT statement then a UPDATE statement to reorder the LINE_SEQ starting from 1.

Is there any way to avoid the additional SQL statement?

I tried with <key column="QUOT_SEQ" not-null="true" update="false"/>
Then, I will get 1 INSERT statement but the LINE_SEQ will be starting from 0.

Cheers,
Eddie

Just curious why do you need the index to start from 1?

Probably brain dead but cannot imagine a use case for that.

When the detail records are listed in the screen, the line seq is start from 1.

I want the actual DB record and on-screen numbering are consistent to avoid any confusion.

Personally, I think it is OK to have the sequence start from 0 in DB and have it displayed as S+1 because there are so many 'confusing' moments:
For example a field in a record holds a foreign key to another record, but we tend NOT to display the FK, but rather some fields from the linked record/object. Another example would be numeric codes like 0..n which correspond to some status information like 'new','in process', 'failed', etc. that gets displayed according to user language.

PS: perhaps H should not perform an extra query, but I tend to forgive H in this case.

It's OK. I just wonder if there is any mis-configuration that cause the extra SQL statement.

Besides, I want to emphasis that the setting update="false". If I set it inside <key column=.. update="false"/>, base="1" will be ignored. The resultant records will be starting from 0,1,2,....

It will be nice if the doc tell us more about the list-index information.

open a bug report