Re: hibernate question ?
On Fri, 27 Aug 2010, Lew wrote:
On 08/27/2010 04:47 AM, mike wrote:
I have an entity like
@Entity
public class Address {
@Id
private int id;
private String street;
private String city;
private String state;
private String zip;
private Set<Address> addressSet = new HashSet<Address>();
public int getId() {
return id;
}
public void setId(int id) {
this.id = id;
}
...
@OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY,
mappedBy = "address")
public Set<Address> getAddressSet() {
return this.addressSet;
}
public void setAuthDevices(Set<Address> address) {
this.addressSet = address;
}
}
and entity :
@Entity
public class Student {
@Id
private int id;
private String name;
@ManyToOne(cascade=CascadeType.PERSIST)
Address address;
public int getId() {
return id;
}
public void setId(int id) {
this.id = id;
}
...
}
if i [sic] do this :
Student emp = new Student();
emp.setId(1);
emp.setName("name");
Address addr = new Address();
addr.setId(1);
addr.setStreet("street");
addr.setCity("city");
addr.setState("state");
emp.setAddress(addr);
addr.getAddressSet().add(emp);
em.persist(emp);
the cascade attribute works and two insert are generated(cascade persist
works, but whenI do something like this :
Student emp = em.find(Student.class, 1L);
emp.setName("name");
Address addr = em.find(Adress.class, 1L);
addr.setStreet("streetOne");
emp.setAddress(addr);
em.persist(emp);
two sql updates are generates and address and student is updates, but
there is NO cascade = MERGE on Student entity... how is this POSSIBLE ?
There's no need to shout so loudly.
I suspect but do not know that it has to do with mixing field and method
annotations in the same class. Don't do that anyway.
It might be coincidence that the cascade specified in the class where you did
that is the one that didn't work.
You probably don't need to initialize 'Address#addressSet' explicitly. I'm
puzzled why people do that in entity classes. What does it provide?
The ability to say new Address().getAddressSet().add(something) without
getting a NullPointerException. Didn't we talk about this before?
I'm more concerned about the setter for the ID field myself.
Well, and the fact that the OP has put the address set in the address
rather than in the student, that the setter for it is called
setAuthDevices, that he calls his Student variable 'emp', and various
other small signs that he has no idea what he's doing.
tom
--
Why did one straw break the camel's back? Here's the secret: the million
other straws underneath it - it's all mathematics. -- Mos Def