Hi,

I am looking at the feasibility of moving a project from TopLink to Hibernate. We are using DB2 as the database. One of the limitations we have with TopLink is that it only supports one updateable mapping per table. Is Hibernate able to support multiple updateable mappings to the same table?

We can sort of workaround the limitation in TopLink because DB2 supports "simple" updateable views which allow us to create more than one mapping, but the solution doesn't feel good.

Thanks,
BraileTrail

If you can model the table using distinct Classes for each updatable chunk, then yes, no problem. If you want a single class to model the table, then you have to write an update "query" for each way of updating the table. For this, you need hiberante 3.1 or later, but it is reasonably comprehensive. When you save an object, the normal update is executed; to use one of the alternatives, you need to get the query, set the object as a parameter to the query, then execute it. It's no more complicated, it just requires a separate save method or what-have-you.

Hi,

thanks for the reply.



Yes, that's exactly what I intended to do. So that is another big plus point for Hibernate.



That is not a option I had considered, but I will give some thought now. :-)

Thanks again,
BraileTrail

If you can model the table using distinct Classes for each updatable chunk, then yes, no problem. If you want a single class to model the table, then you have to write an update "query" for each way of updating the table. For this, you need hiberante 3.1 or later, but it is reasonably comprehensive. When you save an object, the normal update is executed; to use one of the alternatives, you need to get the query, set the object as a parameter to the query, then execute it. It's no more complicated, it just requires a separate save method or what-have-you.

Heh, I just found a problem with Firefox's sessionsaver plugin :) Sorry for the repost, it wasn't me, it was my browser!