Re: Decomposed m:n mapping with ojb and jdo

2005-01-29 Thread Christoph Hermann
Christoph Hermann schrieb: Hello again, The problem seems to lie here: !-- ProfileMenuCategory -- class-descriptor class=papillon.ProfileMenuCategory table=rel_profiles_menu_categories field-descriptor name=profile_id column=profiles_id jdbc-type=INTEGER primarykey=true /

Re: Decomposed m:n mapping with ojb and jdo

2005-01-29 Thread Thomas Dudziak
Both your references use a primarykey part as their foreignkey. Is this really what you want ? The referenced objects must then have the same primarykey value (part) as the ProfileMenuCategory object, and that before you store the ProfileMenutCategory object, otherwise you would overwrite your

Re: Decomposed m:n mapping with ojb and jdo

2005-01-29 Thread Christoph Hermann
Thomas Dudziak schrieb: Hello, Both your references use a primarykey part as their foreignkey. Is this really what you want ? The referenced objects must then have the same primarykey value (part) as the ProfileMenuCategory object, and that before you store the ProfileMenutCategory object,

Re: Decomposed m:n mapping with ojb and jdo

2005-01-29 Thread Christoph Hermann
Thomas Dudziak schrieb: Hello, You should not use the primarykey for this. It would be better if you add a simple primarykey field to the ProfileMenuCategory, make the other two fields normal fields, and in the database add a unqiue constraint on these two fields. This way, the database will

Decomposed m:n mapping with ojb and jdo

2005-01-28 Thread Christoph Hermann
Hello, i try to realize an m:n mapping using ojb/jdo and update the java classes with cocoon using cforms. My problem ist, that i don't get the intermediate table to update correctly in the database. I have the following three classes: public class Profile implements Serializable {