Hi all,

we are integrating with a bought product and we don't want to manage their tables on the database. For these reason and for performance, we are going to manage these data over views.
In our developments, we are creating new tables (i.e travel requests table) and we are doing a join with a view (i.e in the travel requests table we store the user ID and we've got all the user information on a view).
With this scenario, we've got an entity that includes a @OneToMany relationship between travel request and user information.
We don't have any problem to retrieve the data but when we try to insert a new register on the database (a new travel request), we receive an exception becasuse JPA is trying to modify the view (thing that we don't want to do, we only need to insert a new register into the travel requests table).
We are thinking about to create two different entityes, one for select statments with the join explained above and other one for insert / update statments only mapped to the travel requests table.
Is this the best way to do that? Is there any other better approach to do this?

Kind regards,

Ivan.-

specify the cascade for the table view relation with cascade="none"

I'm using Spring + JPA 1 and this kind of Cascade type is not supported. The supported types are:ALL, MERGE, PERSIST, REFRESH and REMOVE.

Well I think that by default no operation is cascaded. So if you don't specify any cascade for the relation then it should be equivalent to cascade=none.

If tht doesn't work then try this