Hibernate uses the database as a reliable data store for serialized objects. It does not exploit the higher level capabilities of the database to assist with referential integrity or the benefits of a more normalized form. (At least it looks that way in examining the results of its UML to data schema translations.)

If that is sufficient for your needs it should be OK. If you need any of these higher level functions or want to access the database efficiently through alternate means (e.g. ETL to DSS stores) this may present an issue.

-david-

Tak Yoshida wrote:

I think,

If you don't have to work with DBA to tune up your application's SQL
or
if you don't have to work with or share SQLs to any backend PL/SQL programmer
or
you don't know SQL very much
The answer could be Hibernate.

If yes, as usual enterprise applications, iBATIS could be the answer.

Tak

Milson Cardona wrote in <[EMAIL PROTECTED]>


Hi

I am novice in J2EE.

I have been working with JDBC (SQL statements within of business
class), but now desire to work with persitence objects.

I know that this are different, Hibernate is then biggest, but iBatis
have a knowledge curve very short....

what do you suggest me?  iBatis or Hibernate.

thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to