By jsugrue
via java.dzone.com
Published: Jun 14 2008 / 00:24
I previously blogged about the shortcomings of JDBC and its way of passing SQL statements as strings without any compile-time checking or type safety. The same also applies to other SQL-based database access libraries such as Microsoft’s ODBC, OLE DB and ADO.NET. None of these APIs provide proper integration of SQL with the host language. Of course you could argue that object-relational mapping (ORM) tools like Hibernate have eliminated the need to work directly with SQL, but I found that there are still situations where you want to control database operations more explicitly.
Comments
raveman replied ago:
re-re-re-re-re-reinventing the wheel. use spring or maybe go crazy and try hibernate?i think its not overkill even for standalone apps.
Motion Control replied ago:
Spring Jdbc is less than you need (no mapping), Hibernate is more (complexity) than you need.
Voters For This Link (14)
Voters Against This Link (1)