starting indexes at 1 instead of 0?

grimholtz · **Joined:** Fri Nov 05, 2004 2:13 pm **Posts:** 7

Hi,
I'm saving a List/Set to a table, and each element's index in the List is also being saved. The indexes start at 0, but I'd like them to start at 1.

What's the best way to do this?

Thank you in advance for any advice.

Sincerely,

grimholtz

Here's my (shortened) hbm.xml:

Code:

<hibernate-mapping package="com.test.foo">
  <class name="QuickQuoteBean" table="quick_quote">
    <id name="quoteID" column="quick_quote_id">
    <generator class="increment"/>
  </id>
  <property name="quoteName" column="quick_quote_name"/>
  <list name="buildings" table="quick_quote_building">
    <key column="quick_quote_id"/>
    <index column="bldg_nmbr"/>
    <composite-element class="BuildingBean">
      <property name="zipCode"/>
      <property name="yearBuilt"/>
    </composite-element>
  </list>
  </class>
</hibernate-mapping>

anthony · **Posted:** Wed Dec 15, 2004 3:21 pm

Quote:

The indexes start at 0, but I'd like them to start at 1.

why because you don't have a record with 0?

i'm afraid you can't, if you don't really need ordered collection, use a bag

grimholtz · **Joined:** Fri Nov 05, 2004 2:13 pm **Posts:** 7

The table is used by a legacy application which expects numbering to start at 1. I do need an orderd collection, so a Bag won't work.

Is there no way to do this? What about using a Map whose keys are Integers (1-n) and whose values are the beans to be stored?

That seems like a kludge to me, but it's the only solution I can think of... would that work?

thank you,
grimholtz

anthony · **Posted:** Wed Dec 15, 2004 3:50 pm

what is bad in having the first element (index = 0) null?

grimholtz · **Joined:** Fri Nov 05, 2004 2:13 pm **Posts:** 7

There are two applications using the same table. The old application cannot be changed, and it expects indexes to start at 1. The new application -- it uses Hibernate -- writes indexes starting at 0, breaking the old application.

In order for the new application (with Hibernate) to work with the old one, it must write indexes starting at 1.

Does that make sense?

Thanks,
grimholtz

steve · **Posted:** Wed Dec 15, 2004 4:09 pm

So why not follow anthony's suggestion and just have the first element in the collection (i.e., index=0) be null?

grimholtz · **Joined:** Fri Nov 05, 2004 2:13 pm **Posts:** 7

ohhhh... I didn't understand that was his suggestion. Thanks! I'll give that a try. Much cleaner than the Map idea.

Thanks very much for your help!

grimholtz