Cascade with index-many-to-many

wilken · **Posted:** Wed Feb 25, 2004 7:58 am

I'm having some trouble getting cascading saves working with a map. I have a class Digest which contains a map of Query objects and number of occurance pairs. Since I am using an object a a key in the map, I used an index-many-to-many association for the map's index.

The problem arises whrn I try to save an instance of the Digest class. Nothing related to the map is saved... no Query objects and no relationship information in the Map table. Since I have cascade set to 'all', I expected a save of the Digest object to save all the objects and data int he map.

Is this a correct expectation? Everythign seems to work as I would expect if the map uses a String or Int as a key (and then not using the index-many-to-many association). Does the index-many-to-many change cascade sematics?

-mike

This is the mapping for my 'Digest' class, which contains a map of Query objects and number of times that query occured.

Code:

<?xml version="1.0"?>
<hibernate-mapping>
    <class
        name="no.fast.vespa.model.reporting.test.Digest"
        table="Digest"
        dynamic-update="false"
        dynamic-insert="false"
    >

        <id
            name="id"
            column="id"
            type="java.lang.Long"
            unsaved-value="null"
        >
            <generator class="native">
            </generator>
        </id>

        <map
            name="querys"
            table="Querys"
            lazy="false"
            sort="unsorted"
            inverse="false"
            cascade="all"
        >

              <key
                  column="digest_id"
              />

              <index-many-to-many
                  class="no.fast.vespa.model.reporting.test.Query"
                  column="query_id"
              />

              <element
                  column="occurances"
                  type="integer"
                  not-null="true"
                  unique="false"
              />

        </map>

        <property
            name="name"
            type="java.lang.String"
            update="true"
            insert="true"
            column="name"
            not-null="true"
            unique="false"
        />

        

    </class>

</hibernate-mapping>

And this is the actual Query class

Code:

<hibernate-mapping>
    <class
        name="no.fast.vespa.model.reporting.test.Query"
        table="Query"
        dynamic-update="false"
        dynamic-insert="false"
    >

        <id
            name="id"
            column="id"
            type="java.lang.Long"
            unsaved-value="null"
        >
            <generator class="native">
            </generator>
        </id>

        <property
            name="queryTerm"
            type="java.lang.String"
            update="true"
            insert="true"
            column="queryTerm"
            not-null="true"
            unique="true"
        />

     

    </class>

</hibernate-mapping>

emmanuel · **Posted:** Wed Feb 25, 2004 9:06 am

Did you set equals/hashCode of Query ?

wilken · **Posted:** Fri Mar 05, 2004 11:28 am

Quote:

Did you set equals/hashCode of Query ?

Yes, I implemented hashcode() and equals(), using the 'semi-unique key with business meaning' strategy discussed at http://hibernate.org/109.html... here is the actual code

Code:

    public boolean equals(Object obj) {
        return (obj instanceof no.fast.vespa.model.reporting.test.Query
                && this.queryTerm == ((Query) obj).getQueryTerm());
    }

    public int hashCode() {
        return 17 * this.queryTerm.hashCode();
    }

wilken · **Posted:** Fri Mar 05, 2004 12:26 pm

I have played with this some more, and found another twist I don't understand. If I run the following code with the flush() commented out, it saves the digest object, but not the contained Query object. But if I run it with the flush() uncommented, I get a transient object exception. Is this expected behavior, or I am jsut completely confused about what I am trying to do?

Code:

Digest d = new Digest();
d.setName("Test Digest");

Query q = new Query("test query 1");
d.addQuery(q);
Session s = this.sf.openSession();
s.save(d);
//s.flush();
s.close();

Thanks again, -mike

wilken · **Posted:** Mon Mar 08, 2004 10:27 am

Bump... still confused and needing some help :-)

snek · **Joined:** Thu Dec 11, 2003 6:21 am **Posts:** 8

As far as I know cascades are not supported for collection indexes.

emmanuel · **Posted:** Mon Mar 08, 2004 6:53 pm

snek wrote:

As far as I know cascades are not supported for collection indexes.

You are mistaken. Bidirectional mapping is not supported.