Hibernate version:
3.1.3

Mapping documents:


Name and version of the database you are using:
MySQL 5

1. If I have nothing, but classMetadata how can I find what set is inversed (e.g. to prohibit editing the other one)

2. If I do "children.add(parent)" is there a way to synchronize the child and the parent without sending data to server and retreiving them back?

I'm not quite sure what you mean in #1, but prohibiting editing is not something usually associated with the persistence layer of an application. Do you mean making one of the tables "read-only" so that updates will not occur to existing rows?

For the second question, when you are handling the persistent objects using the POJO/OO-like hibernate approach, Hibernate will be making the decisions about what needs to be sent back and forth between the database server and the client applications. It obviously has to update the database when you establish a new relationship for a persistent object or add a new persistent object. Presumably Hibernate does not send data back again from the database unless it needs to, in which case you don't really have a choice regardless of your approach. For example, there could be a property in the persistent object that corresponds to an automatically generated Id. Hibernate would have to retrieve that value so that it could be placed in the persistent object representing that new row.

OK, I'll try to explain.
Imagine that you have Class C persisted in a database.
You also have Configuration, SessionFactory, Session, ClassMetadata etc.

The goal is to write a component which allows to edit set of instances of C:



In case of many-to-many relationship after editing the object with SetEditor I have to update all related objects. At present I have no idea how to do it.

There is a number of workarounds of how to do this.

1. I only allow to edit one side of association (where inverse=false). Thus user have no ability to edit or view another side so I have nothing to synchronize (let's suppose application that USES the data is another one)
This is what my first question was about.
2. I set both associations to have inverse=false and after changing any set always commit the transaction. This has two bad issues:
(i) I have to send extra data there and back again (this is what my second question was about)
(ii) I cannot rollback after I made a commit.

Heh?