Re: [cinjug-users] hibernate 3.0 usage

[Kedar Jog <kedar.jog@xxxxxxxxx>]

If your are doing true CRUD (Create READ Update Delete) using
hibernate you are doing fetch ops for the READ anyway.....
Actually Hibernate does an extremely good job in fetch ops , using
lazy collections ensures that only "light" objects are brought back...
I would use JDBC only if your Object graph is very deep and only
subsections of the data are needed i.e one attribute from one object
and another attr from a child object etc .... For ex: displaying
search results etc...


 


On 8/1/05, Akalamkam, Pardha <Pardha.Akalamkam@xxxxxxxxxxxxxxxx> wrote:
> Hi All,
>  
>   In our project we are using hibernate 3.0 (portal project).
>   It was informed to us all, that only to use Hibernate 3.0 , when it
> requires all database operations(CRUD).
>   If it's only fetching, then to use regular JDBC.
>  
>  My question to you all is, if we use Hibernate for fetching also, does it
> increases overhead or it's OK to use it for all database operations.
> Please provide me your valuable suggestions.
>  
>  
> Pardha


-- 
Regards 

Kedar 

-----------------------------------
Kedar Jog 
5908 Monassas Run Rd 
Milford OH 45150