Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Why iBatis is an ORM ?

 
Hussein Baghdadi
clojure forum advocate
Bartender
Posts: 3479
Clojure Mac Objective C
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hola.
Why iBatis considered as an ORM ?
AFAIK, iBatis uses SQL maps which means you still have to write SQL by your bare hands while other ORM tools (e.g Hibernate) generate a great amount of SQL ?
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
iBatis is not an ORM. Take some time and read some of the other posts and you'll see the author state this. Primarily in the iBatis vs Hibernate threads.
 
Brandon Goodin
author
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Because "the man" likes to categorize the innovators ;-)

You are correct we are not a classic ORM. But, we do provide a means to bridge the Object Relational conundrum. iBATIS was not built to cater to the the OO purist propeller heads or the dictatorial database admins. It was built to help them get along. I guess anyone who works towards that effort lands in the ORM category. It's fine with me because it gives us a voice in an audience that could use us.
 
Paul Casal
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
iBatis is not an ORM tool. It does not track changes to the objects that are mapping data, so it won't generate the SQL updates for you. Still, many people out there do not need all the features of an ORM so why pay the price (in learning curve and even performance)? iBatis can do the job in many cases.
 
Timothy Toe
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
AFAIK there is no hard and fast rule on how to categorize a tool as an ORM tool or not.

I think any tool that attempts to bridge the gap or assist in bridging the OO-Relational DB gap can be considered to be in the ORM space.

Some ORM tools automate more and some less, that's all. Those that automate more usually tradeoff performance ... and those that automate less usually give more fine-grain control.

One good thing I find in iBatis is that, it does not invent/introduce its own query language (Entity Beans has its own EJB-QL and Hibernate has its own HQL). iBatis, instead, encourages you to code with the very mature, industry standard, SQL. This reduces the learning curve considerably and also make learning it a worth while effort as you'll never go wrong learning SQL - you know what you learn will last a longer time.

Feel free to correct me if any fact above is wrong.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic