OK, per your request: I just talked to a developer who works for a
company that I worked with last summer (both of them will remain
nameless).
While I was there, we had a mapped statement that was a monster -
about 300-400 lines long when you combined the result map and the sql
statement. To run
Thank you all for some great feedback. Especially the 2 for 1 deal from
Clinton - an ORM discussion and a history lesson :)
However, I'm still in search of "answers" - maybe it's because I'm not sure
what it is I'm asking for, kind of like the answer to the ultimate question
;)
I have tried Hib
This might be a good read.
http://www.mail-archive.com/ibatis-user-java@incubator.apache.org/msg01251.h
tml
_
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: Monday, December 18, 2006 11:37 PM
To: user-java@ibatis.apache.org
Subject: Re: ibatis v hibernate
The
The problem with pros and cons is that they change almost on a per project
basis.
I'd suggest just adding the above comments to the "Feedback and experiences"
section of the wiki page.
Cheers,
Clinton
On 12/18/06, Eric T. Blue <[EMAIL PROTECTED]> wrote:
IMHO, I think Larry and Nathan are bot
IMHO, I think Larry and Nathan are both partially right. I believe it's
safe to say that discussions on the topic of persistence frameworks in Java
are sometimes as intense as political or religious debates ;) Personally, I
think a high-level breakdown of the differences between frameworks would
How about a more general description of the differences and usage.
BTW there is nothing wrong with stating reasons why our product is better
then others at specific tasks.
Nathan
On 12/18/06, Larry Meadors <[EMAIL PROTECTED]> wrote:
Heh, that it would probably be considered "flame-bait'.
Lar
Heh, that it would probably be considered "flame-bait'.
Larry
On 12/18/06, Nathan Maves <[EMAIL PROTECTED]> wrote:
These are all great success stories. Coming from someone who has never
tried Hibernate I love reading these. What are some thought about putting
together a page about IBATIS vs
MAIL PROTECTED]
*Sent:* Saturday, December 16, 2006 3:24 PM
*To:* user-java@ibatis.apache.org
*Subject:* Re: ibatis v hibernate
I'll let the user community speak to the practical experiences, but at a
practices level consider the following at a philisophical level.
All databases are legacy databa
_
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 16, 2006 3:24 PM
To: user-java@ibatis.apache.org
Subject: Re: ibatis v hibernate
I'll let the user community speak to the practical experiences, but at a
practices level consider the following at a philisophical l
>From: Clinton Begin [mailto:[EMAIL PROTECTED]
>http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx
Thank you very much, I enjoyed that thoroughly. :)
I've used both quite extensively (1 year plus projects). I think it's
important to take a step back and look at what you are trying to optomise. The
real goal of any ORM tool is to reduce the amount of code you write and
therefore increase your developer efficiency while reducing your bugs and
Hello,
My group currently uses iBATIS with several 'from scratch' data models. We
used Hibernate as an experiment on one data model before settling on iBATIS for
everything. What I would say about the two is that if you don't know SQL and
you don't want to know about SQL and you have large da
I'll share my story on this, too, but will say up-front that I am
(obviously) an iBATIS advocate.
I was an early adapter of ORM. I started with Hibernate 1.x before I
had ever heard of iBATIS. After a week or so a friend (who had also
used ORM - in the form of JDO) warned me that I would not like
I'll let the user community speak to the practical experiences, but at a
practices level consider the following at a philisophical level.
All databases are legacy databases. Any database that is of any value will
ultimately become a dependency for more than the original application it was
built
14 matches
Mail list logo
