m: Nathan Maves [mailto:[EMAIL PROTECTED]
Sent: Monday, January 23, 2006 12:32 PM
To: user-java@ibatis.apache.org
Subject: Re: iBatis usage pattern
I agree with Jeff,
The whole point of ORM is that both can be developed independently.
You might have one class that is represented by multiple
I agree with Jeff,The whole point of ORM is that both can be developed independently. You might have one class that is represented by multiple tables or the opposite case where multiple class are store in one table.I would suggest, like Jeff, making sure that your domain model is implemented with
Well I don't think it's exactly the concept of ORM. ORM normally says that database design isn't as important as object design. The philosphy with ORM is that the object model rules all decisions, and that the database model should be subservient to the object model. I don't think this is realis
anuary 21, 2006 6:10 AM
To: user-java@ibatis.apache.org
Subject: Re: iBatis usage pattern
Hi Yusuf,
This is a big question!
Clinton is right that a JavaBean will be faster, but I've always thought
that the performance gain will be negligible and not noticed by any
user. For me, this is
Hi Yusuf,
This is a big question!
Clinton is right that a JavaBean will be faster, but I've always thought that the performance gain will be negligible and not noticed by any user. For me, this is not enough of an argument one way or the other.
I have been on both sides of the issue with M
Hello,
I've been using ibatis for quite some time now, and I like to ask some
questions to all ibatis gurus out there...
- For queries with joins from many table, i usually map results to a Map
(no need to make custom beans), for example:
SELECT *
FROM dept, emp, bonus
