Re: JDBC vs Hibernate
- From: Luke Webber <luke@xxxxxxxxxxxxx>
- Date: Fri, 09 Sep 2005 16:23:41 +1000
Sandy wrote:
"Luke Webber" <luke@xxxxxxxxxxxxx> wrote in message news:4320df5f$1_3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
It really depends on a number of factors. Do you really want database indepence, or are you happy to stick with one DBMS? How complex is the SQL going to get? Do you need automatic dirty checking and optimistic locking?
My application is fairly simple, its using one database only that will never change. I just need to put the data in tables, thats all, no further SQL queries. and there are no objects which are mapping to two different tables (so i don't need complex SQL logics)
I feel JDBC is better (performance and development time wise) than hibernate in my case.
Is there any other thing that i should consider before making the decision.......
I think you've answered your own question. JDBC is fine for your needs. No point in adding extra layers and increasing complexity.
Luke .
- Follow-Ups:
- Re: JDBC vs Hibernate
- From: Sandy
- Re: JDBC vs Hibernate
- References:
- JDBC vs Hibernate
- From: Sandy
- Re: JDBC vs Hibernate
- From: Luke Webber
- Re: JDBC vs Hibernate
- From: Sandy
- JDBC vs Hibernate
- Prev by Date: Re: JDBC vs Hibernate
- Next by Date: Re: JDBC vs Hibernate
- Previous by thread: Re: JDBC vs Hibernate
- Next by thread: Re: JDBC vs Hibernate
- Index(es):
Relevant Pages
|
|