?

?

There's been a certain amount of noise recently surrounding simple JDBC frameworks like iBATIS. I've liked the idea of iBATIS myself, for use in applications which don't need an object-oriented domain model, and don't work with deep graphs of associated entities in a single transaction. A JDBC framework also makes good sense if you are working with some kind of "insane" legacy database; ORM solutions tend to assume that associations are represented as nice clean foreign keys with proper referential integrity constraints (Hibernate3 much less so than Hibernate 2.x).

?

Some people even suggest that JDBC frameworks are a suitable alternative to ORM, even for those systems to which ORM is best suited: object-oriented applications with clean relational schemas. They argue that you are always better off with hand-written SQL than generated SQL. Well, I don't think this is true, not only because the overwhelming bulk of SQL code needed by most applications is of the tedious kind, and simply does not require human intervention, but also because a JDBC framework operates at a different semantic level to ORM. A solution like iBATIS knows a lot less about the semantics of the SQL it is issuing, and of the resulting datasets. This means that there is much less opportunity for performance optimizations such as effficent caching. (By "efficient", I am referring mainly to efficient cache invalidation strategies, which are crucial to the usefulness of the cache.) Furthermore, whenever we have seen handwritten SQL, we have seen N+1 selects problems. It is extremely tedious to write a new SQL query for each combination of associations I might need to fetch together. HQL helps significantly here, since HQL is much less verbose than SQL. For a JDBC framework to be able to make the kind of optimizations that an ORM can make, it would have to evolve to a similar level of sophistication. Essentially, it would need to become an ORM, minus SQL generation. In fact, we already start to see this evolution taking place in existing JDBC frameworks. This begins to erode one of the stated benefits: the claimed simplicity.

?

It also raises the following interesting thought: if, by gradually adding stuff, a JDBC framework will eventually end up as ORM, minus SQL generation, why not just take an existing ORM solution like, ooh, um ... Hibernate, maybe ... and subtract the SQL generation?

?

The Hibernate team has long recognized the need to mix and match generated SQL with the occasional handwritten query. In older versions of Hibernate, our solution was simply to expose the JDBC connection Hibernate is using, so you can execute your own prepared statement. This started to change a while ago, and Max Andersen has recently done a lot of work on this. Now, in Hibernate3, it is possible to write an entire application with no generated SQL, while still taking advantage of all of Hibernate's other features.

?

Do we really expect or intend people to use Hibernate in this way? Well, not really - I doubt there are many people out there who really enjoy writing tedious INSERT, UPDATE, DELETE statements all day. On the other hand, we do think that quite a few people need to customize the occasional query. But to prove a point, I'll show you how you can do it, if you really want to.

?

Let's take a simple Person-Employment-Organization domain model. (You can find the code in the org.hiberna

推荐阅读更多>

1. oracle 用户 逾期处理
2. ODI中新增插件(Open Tools)引见
3. MongoDB的下令
4. BIEE oc4j没法启动
5. MySQL数据库的优化（下）单机MySQL数据库的优化
6. 配备Oracle stream（3）
7. Oracle挟制使用索引
8. 将数据库select出来的数据转化为与呼应databean对应的字典
9. 对数据库连接池的一些批改
10. BoneCP 0.6.4公布，高效的Java数据库连接池
11. SQL2000管理SQL7服务器出现TIMEOUT问题的解决
12. 关于页面刷新到一定数量后回绝从数据库中查询
13. utl_url.escape步骤
14. 存储过程仍是业务逻辑层
15. 第八章 数据修改(二)
16. IOS学习之IOS沙盒(sandbox)机制和资料操作(一)
17. 强烈推荐一个简略而实用的数据库连接池工程
18. Oracle分页的两种形式
19. Win7安装Oracle 10G的有关问题
20. H2数据库的施用入门