For our next project we decided to use hibernate framework.But my Project Manager have worked experience in tomcat torque who point out some problem when he using ORM framework...
1.We cannot managing db connection( open and close)
2.more complexity when using join query
3.store procedure not supporting
4.suppose student table we need DOB only but in ORM supporting whole object access any performance issues this kind of access.
5.
how hibernate solving these problem,
please suggest me.....
i want clarify few question further
Normally all are go for stored procedure even a single query execution due to high performance,relation and calculation.i need comparison of caching and stored procedures,caching increase only the data access time(if same data access multiple users simultaneously)not table modification,however in normal application most of the query is written for table modification,so how hibernate caching support table modification and i think EnterpriseJavaBean3.0 and hibernate are identical other than naming convention ,is there any different between EnterpriseJavaBean3.0 and hibernate based on Object Relational Mapping.
|