On Sun, 25 Apr 2010, Arne Vajh?j wrote:
On 25-04-2010 01:03, Jack wrote:
When I work on database development projects, I use JDBC and SQL. Many
people use hibernate/spring. Can somebody explain the pros and cons of
using JDBC and SQL vs using hibernate/spring on database
developments?
That is a rather big discussion.
The ultra short version is:
- ORM (Hibernate or other) is best when the problem to
be solved is CRUD of objects
- pure SQL (JDBC) is best when you want to do something
more unusual
I'd rephrase that slightly to say that ORM is best when you want to deal
with your data as objects - when you need to be able to call methods,
traverse object graphs, and generally think of your data as objects.
If your data is something that isn't usefully thought of as objects
(perhaps a big boring spew of temperature measurements over time or
something) then there isn't much benefit to ORM. There's probably no
real harm either, so if you prefer ORM, you can still use it.
And as Arne said, when you're trying to do something unusual, you may be
outside the limits of what ORM can comfortably do, and you'll be better
off using straight JDBC. Or perhaps a combination of ORM for any CRUDdy
/ domain logicky bits, and JDBC for complex queries.
lots of potential consistency issues. I would avoid it if possible.