Butler wrote:
> > See here:
> >
> > http://issues.apache.org/jira/browse/IBATIS-375
> >
> > Looks like a fix for this is in 2.3.4.
> >
> > Jeff butler
> >
> >
> > On Tue, Jan 6, 2009 at 3:42 PM, Hugh Ross wrote:
> >>
> >
ike a fix for this is in 2.3.4.
>
> Jeff butler
>
>
> On Tue, Jan 6, 2009 at 3:42 PM, Hugh Ross wrote:
>>
>> We are testing some sqlMaps to avoid the N+1 Selects problem that include
>> OUTER JOINs. Since nulls are coming back in the Result Sets, we are seeing
>> po
See here:
http://issues.apache.org/jira/browse/IBATIS-375
Looks like a fix for this is in 2.3.4.
Jeff butler
On Tue, Jan 6, 2009 at 3:42 PM, Hugh Ross wrote:
>
> We are testing some sqlMaps to avoid the N+1 Selects problem that include
> OUTER JOINs. Since nulls are coming ba
We are testing some sqlMaps to avoid the N+1 Selects problem that include
OUTER JOINs. Since nulls are coming back in the Result Sets, we are seeing
pojos created with all nulls. Testing with iBatis 2.3.4.
I don't recall seeing this problem mentioned before, but I can't believe no
on
Haha, problems are repeating ;-).
If I get this right, we just had this 2 days ago, had we not?
Take a look in this thread:
http://www.nabble.com/Having-two-N-plus-1-groups-p18361780.html
I'll go with RowHandler and check if it works with collection-types somehow.
Cheers
Heinrich
mailjoe wro
Good point Larry! My domain objects look like this:
Restaurant --> waitersTeam --> John, Tim, Cindy
--> managersTeam --> Mary, Steven
I have SQL Maps for both the waitersTeam and the managersTeam.
Now, I want to fetch Restaurant objects with a single query based on INNER
JOIN.
T
FWIW, I got as far as "COMPLEX", "A_GROUP", and "B_GROUP" before I
stopped reading. ;-)
I'm not saying no one else will read or answer you, just that I think
if you can make this a more concrete example, instead of a tuple
calculus exercise, then you might get more (and better) responses.
Larry
Hi,
We have a ComplexObject made of one instance of aGroup and one instance of
bGroup.
The aGroup is made of a collection of A instances.
The bGroup is made of a colleciton of B instances.
We have one SQL Map for aGroup, and another one for bGroup.
If aGroup contains m A's and bGroup contains n
: n+1 selects and queryForMap
Hello,
I have an object with a property that is a HashMap of name/value pairs from a
separate data table. If one of my properties on the 'food' class is a hashmap,
I'm assuming I can create that hashmap using the following sql mapping correct?
Is
Hello,
I have an object with a property that is a HashMap of name/value pairs from a
separate data table. If one of my properties on the 'food' class is a hashmap,
I'm assuming I can create that hashmap using the following sql mapping correct?
Is it possible to avoid the n+1 select issue and so
Subject: RE: Newbie tries to solve the N+1 selects problem and cries for
help
In this case, you have to implement a row handler.
Christian
From: Brian Parkinson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 12:14 PM
To: user-java
In this case, you have to implement a row handler.
Christian
From: Brian Parkinson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 12:14 PM
To: user-java@ibatis.apache.org
Subject: Newbie tries to solve the N+1 selects problem and cries for
help
Hello:
I am having a problem with the ol' N+1 selects problem - wondering if
someone can help.
I have a Status object, which contains a list of StatusEquipment
objects, as well as a list of StatusZone objects. I want, in one select
statement, to retrieve the one Status object, and pop
Well, if you want to hire me to fix it, I'll add you to my client list
and get you on the schedule. If it doesn't annoy anyone that much,
we'll have to wait for someone who needs it bad enough to fix it.
:-D
Larry
On 5/16/07, Stefan Langer <[EMAIL PROTECTED]> wrote:
Larry Meadors schrieb:
> O
Thanks for your help, the problem was with the null values in the left join.
Carlos
On 5/16/07, Stefan Langer <[EMAIL PROTECTED]> wrote:
Larry Meadors schrieb:
> On 5/16/07, Stefan Langer <[EMAIL PROTECTED]> wrote:
>> See issue https://issues.apache.org/jira/browse/IBATIS-375 and please
>> v
Larry Meadors schrieb:
On 5/16/07, Stefan Langer <[EMAIL PROTECTED]> wrote:
See issue https://issues.apache.org/jira/browse/IBATIS-375 and please
vote for it if you find it annoying.
...or even better, get the code from SVN and attach a patch. :)
Larry
If I could find the time I would go for
On 5/16/07, Stefan Langer <[EMAIL PROTECTED]> wrote:
See issue https://issues.apache.org/jira/browse/IBATIS-375 and please
vote for it if you find it annoying.
...or even better, get the code from SVN and attach a patch. :)
Larry
Not sure it is related to your issue but be aware that when you do a
left outer join and you have no results for the left join you will still
receive a row containing only nulls for your left joined object. IBatis
will try to fill up your object with these null values. If your code for
some rea
Hi all,
I'm new to iBatis and I'm coverting the existing code to implement iBatis,
so sorry in advance if my questions are too simple.
I have a problem trying to avoid the n+1 selects.
The following Application.xml
te:
> > > > > I guess I'll have to take a different approach. The depth isn't
set to be a defined level; so if I go more than two levels below the
grandparent, it won't work.
> > > > >
> > > > >
> > > > >
> > > > &
on properties using the resultMap
> > > > > attribute.
> > > > >
> > > > >
> > > > >
> > > > > ...
> > > > >
> > > > >
> > > > > ...
> > > > &g
> > > >
> > > >
> > > > ...
> > > >
> > > >
> > > > ...
> > > >
> > > > ...
> > > >
> > > > The select statement should join the tables together and you may
> >
> > > ...
> > >
> > > ...
> > >
> > > The select statement should join the tables together and you may
> > > need to be very explicit with the column names.
> > >
> > > Clinton
> > >
> > > On 2/19
gt; > >
> > > > ...
> > > >
> > > > ...
> > > >
> > > > The select statement should join the tables together and you may
> > > > need to be very explicit with the column names.
> > > >
> > > > Clinton
&g
t; > >
> > > ...
> > >
> > > ...
> > >
> > > The select statement should join the tables together and you may
> > > need to be very explicit with the column names.
> > >
> > > Clinton
> > >
> > > On 2
:11 AM
To: user-java@ibatis.apache.org
Subject: Avoiding N+1 Selects
I have a table which has all of the parent/child relationships in the same
table. I would like to avoid the N+1 selects with this construct, but it's
unclear from the documentation if
.
> >
> >
> > ...
> >
> >
> > ...
> >
> > ...
> >
> > The select statement should join the tables together and you may need
> > to be very explicit with the column names.
> >
> > Clinton
> >
> > On 2/
;
> The select statement should join the tables together and you may need to
be very explicit with the column names.
>
> Clinton
>
>
>
> On 2/19/07, Brad Handy <[EMAIL PROTECTED]> wrote:
> > I have a table which has all of the parent/child relationships in the
same ta
ers.
If your DB has that kind of thing, you could use it and a row handler to pull
the results into what you need.
-Original Message-
From: Brad Handy [mailto:[EMAIL PROTECTED]
Sent: Mon 2/19/2007 8:17 PM
To: user-java@ibatis.apache.org
Subject: Re: Avoiding N+1 Selects
I guess I'll
The select statement should join the tables together and you may need to
> be very explicit with the column names.
>
> Clinton
>
> On 2/19/07, Brad Handy <[EMAIL PROTECTED]> wrote:
> >
> > I have a table which has all of the parent/child relationships in the
> > s
te:
>
> I have a table which has all of the parent/child relationships in the
> same table. I would like to avoid the N+1 selects with this construct, but
> it's unclear from the documentation if this can be done.
>
> Let's say I have the following relationships defined
n
On 2/19/07, Brad Handy <[EMAIL PROTECTED]> wrote:
I have a table which has all of the parent/child relationships in the same
table. I would like to avoid the N+1 selects with this construct, but it's
unclear from the documentation if this can be done.
Let's say I have the fo
I have a table which has all of the parent/child relationships in the same
table. I would like to avoid the N+1 selects with this construct, but it's
unclear from the documentation if this can be done.
Let's say I have the following relationships defined in the table:
Grand Parent
r-java@ibatis.apache.org
cc
Please respond to
[EMAIL PROTECTED] Subject
apache.org Avoiding N+1 Selects(1:M and M:N)
Avoiding N+1 Selects(1:M and M:N)
with iBATIS version 2.1.7
I read the explanation about Avoiding N+1 Selects(1:M and M:N) with
2.2.0, but the version I am using now is 2.1.7.
Is there way I can do this job like 2.2.0 by using 2.1.7? Make sense?
English is not my native language, so please understand me. ^___^
...
select
EMAIL PROTECTED]> wrote:
I'm having a problem with a simple N+1 selects problem.
I have some objects akin to:
Product implements Serializable {
List attributes;
String id;
}
Attributes {
String name;
String value;
}
and I do something along the lines of
W
Because whe you serialize Product, the list of Attribute objects
cannot be serialized, so...kaboom.
Make Attribute serializable, and it'll work.
Larry
On 1/13/06, Perry Nguyen <[EMAIL PROTECTED]> wrote:
> I'm having a problem with a simple N+1 selects problem.
>
> I
I'm having a problem with a simple N+1 selects problem.
I have some objects akin to:
Product implements Serializable {
List attributes;
String id;
}
Attributes {
String name;
String value;
}
and I do something along the lines of
When I go to Serialize Product, I end up
ect, I will be very appreciate.
>
> Thanks,
>
> John Chien
>
>
> Clinton Begin wrote:
> Looks to me like you're:
>
> 1) Using an older version of iBATIS or at least an incorrect DTD reference
> that does not support [EMAIL PROTECTED]
> 2) You're us
Clinton Begin wrote:
Looks to me like you're:
1) Using an older version of iBATIS or at least an incorrect DTD
reference that does not support [EMAIL PROTECTED]
2) You're using half of the N+1 selects solutionwhich will not do
much for you.
Perhaps ignore this problem for now, a
Looks to me like you're:
1) Using an older version of iBATIS or at least an incorrect DTD reference that does not support [EMAIL PROTECTED]
2) You're using half of the N+1 selects solutionwhich will not do much for you.
Perhaps ignore this problem for now, and instead state exact
Jean:
Thank you for your response.
That's my fault. My intention actually is not tries to do the N+1
selects, but have returned result putting into a bean.
This bean will be used as a property of another bean.
I do not know if my way of doing it is correct or not. Somehow it does
not
hn Chien [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 3:27 AM
To: user-java@ibatis.apache.org
Subject: N+ 1 selects
Dear Sir:
I follow the FAQ to fix the N+1 selects, However, I continue get the
compilation error.
My xml looks like:
Give us a stack trace, too, please.
Larry
On 9/28/05, John Chien <[EMAIL PROTECTED]> wrote:
> Dear Sir:
>
> I follow the FAQ to fix the N+1 selects, However, I continue get the
> compilation error.
> My xml looks like:
>
>
>
> PUBLIC "-//iBATIS
Dear Sir:
I follow the FAQ to fix the N+1 selects, However, I continue get the
compilation error.
My xml looks like:
http://www.ibatis.com/dtd/sql-map-2.dtd";>
type="us.nc.state.enr.bets.util.EhsInspectorBean"/>
type="us.nc.state.enr.bets.finder.Common
Hi
According to the documentation it is possible to ommit N+1 selects using
i.e:
What if category has several attributes, I wouldn't like to recopy them to
other resultMap. Adding new attributes, requires
to place it in two or more resultMaps.
I would like just to reuse categoryMap
gt; >
>> >On 6/22/05, Aaron Craven <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> I cannot decide if I've missed something in the documentation, or if I'm
>> >> just plain old confused, but either way I need some help. With iB
aven <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> I cannot decide if I've missed something in the documentation, or if I'm
> >> just plain old confused, but either way I need some help. With iBATIS 2, I
> >> realize the N+1 selects problem ha
n
>
>
>On 6/22/05, Aaron Craven <[EMAIL PROTECTED]> wrote:
>>
>>
>> I cannot decide if I've missed something in the documentation, or if I'm
>> just plain old confused, but either way I need some help. With iBATIS 2, I
>> realize the N+1 selects problem
AIL PROTECTED]> wrote:
I
cannot decide if I've missed something in the documentation, or if I'm
just plain old confused, but either way I need some
help. With iBATIS 2, I realize the N+1 selects problem has
been solved by the addition of the groupBy
property. However, I'm a bit c
n the documentation, or if I'm
>> just plain old confused, but either way I need some help. With iBATIS 2, I
>> realize the N+1 selects problem has been solved by the addition of the
>> groupBy property. However, I'm a bit confused as to how this would be done
>
cide if I've missed something in the documentation, or if I'm just
> plain old confused, but either way I need some help. With iBATIS 2, I
> realize the N+1 selects problem has been solved by the addition of the
> groupBy property. However, I'm a bit confused as to how this w
I cannot decide if Ive missed something in the documentation, or if Im just
plain old confused, but either way I need some help. With iBATIS 2, I realize
the N+1 selects problem has been solved by the addition of the groupBy
property. However, Im a bit confused as to how this would be
54 matches
Mail list logo
