Clinton Begin wrote:
Don't worry, we don't intend to abandon XML. But instead, we intend to
support a more robust Java API to allow developers to do both full
mapped statement configuration from Java, as well as execute ad-hoc SQL
statements.
Cheers,
Clinton
Sounds great! Thanks for the re
Don't worry, we don't intend to abandon XML. But instead, we
intend to support a more robust Java API to allow developers to do both
full mapped statement configuration from Java, as well as execute
ad-hoc SQL statements.
Cheers,
Clinton
On 11/2/05, Ben Munat <[EMAIL PROTECTED]> wrote:
Clinton Beg
Clinton Begin wrote:
No, I would avoid that. I'm not sure what the appeal is of doing
something like this. More XML and less Java? I'm finding the opposite
opinion is more common these daysless XML and more Java. In fact,
one of the highest priority features of iBATIS 3.0 is XML-less
No, I would avoid that. I'm not sure what the appeal is of doing
something like this. More XML and less Java? I'm finding
the opposite opinion is more common these daysless XML and more
Java. In fact, one of the highest priority features of iBATIS 3.0
is XML-less iBATIS. ;-)
Cheers,
Clin
What's a good pattern to perform multiple statements
on a single DAO method. Suppose I have a bunch of
"User" objects each containing a list of "Group"
objects. Right now I'm doing the following:
(Pseudocode)
AddUser(User) {
[BeginTransaction]
Mapper.Instance().Insert("InsertUser", user);
f
