Here's the problem.

We have a webapp in which we can enter data (Timesheets), no problem there. When the user is finished he saves the timesheet in our database. Afterwards he can change the timesheet etc. When he is really finished he submits his timesheet and then the timesheet needs approval of his supervisor.

However no the problem occurs when the timesheet is approved by his supervisor the timesheet needs to me transferred to another database. (We have partitioned data, approved data is in another database then 'draft' data).

We can access the other database from our own schema, so from our point-of-view it is just storing our object in another table. However it is giving us trouble.

We tried different solutions each creating their own problems. Currently we are deciding if we would need plain JDBC for that solution, however it would be nice if we could do it with hibernate.