Just about speed and performance, (exclude object abstraction that hibernate provide), hibernate is a good option ?
If we put all of logic to database using package, stored procedure and trigger, we just call it in the java function, then wrap it to an object.
This pure JDBC design, compared to hibernate, is a good option ? or on what situation it is better solution?
Do we over-use hibernate?
Besides a small potential performance boost,
Business logic in stored procedures is difficult to maintain,/quote]
I agree with you.
ties you too closely to a single RDBMS and limits reuse of the logic
some projects, for example, company internal project, will be OK using a single RDBMS and lose some reuse.
Thank.
Besides a small potential performance boost,
Business logic in stored procedures is difficult to maintain
ties you too closely to a single RDBMS and limits reuse of the logic
how much "performance boost", do we have some test data ?
some projects, for example, company internal project, will be OK using a single RDBMS and lose some reuse.
"This is not to say that design is unnecessary. But after a certain point, design is just speculation." --Philip Chu
Also in our case we need to switch on and off databse indexes which you cannot control thru Hibernate.
Also with the database abstraction layer you can gain extra benefits of stored procedures.
My point being there is nothing wrong in using Oracle specific (or database) features to gain that extra performance.
I am accessing iBatis as it gives more flexibility with sqls.
SCJP, SCWCD
Originally posted by Edward Chen:
Hi, Guys,
I have posted same question to Oracle forum.
http://forums.oracle.com/forums/thread.jspa?threadID=435466&tstart=0
You could see database person's view.
Thanks.
Originally posted by Edward Chen:
I found an article online related to this, maybe it is helpful.
http://www.onjava.com/pub/a/onjava/2003/08/13/stored_procedures.html