Hi All,
I think I'm starting to understand now, well I guess I'm off to
designing a good domain model before trying to do something else :)
And for what it's worth, I think iBatis is still the best out there for
this kind of tool.
Thank You,
Yusuf.
-Original Message-
From: Nathan Maves [
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
Hi Jeff,
So let me conclude your explanation:
It is better to create a good pojo based domain model (bottom line, a
class for each table?) rather than using maps for results (except for
those one-of-a-kind query), and always try to group results to POJOs,
using the "group by" and maybe other ibatis
resultMap="rawAttendanceRecordResult"parameterClass="searchAttendanceRecords"> select * from RAWATTENDANCERECORD
where logDate #fromDate#
and logDate #toDate#
You need to enclose the <= and >= operators in XML CDATA sections to avoid breaking the XML syntax.
The and is tags are for
I have a table called rawattendancerecord.
There is a column in the table called logDate;
I want to be able to return log dates between 2 give
search date criteria. E.g. dates between fromDate and
toDate.
I can do a search from the command line (mysql) with
the following commands to return the