Thanks for posting your solution; you've answered my question as well!
Tell your boss I said it was okay for you to take the rest of the day off. ;)
Ted
On 21/03/07, Mikael Andersson <[EMAIL PROTECTED]> wrote:
Hi,
I had a bit of a breakthrough :)
Ditched the subselect; started experimenting w
Hi Mike,
I see where you found the composite key syntax in the Developer's
Guide ("Composite Keys or Multiple Complex Parameters Properties").
The guide does make it sound like the values are being passed in to
the nested select. I've run out of ideas.
However, when you get this approach worki
Hi,
I had a bit of a breakthrough :)
Ditched the subselect; started experimenting with using resultMap and
groupBy instead of select attribute and got it working.
Important change (for new users):
I assume this is the preferred way of doing things as well, so I'm happy.
Thanks,
Hi
Thanks for the help so far.
I thought that this bit:
wrote:
Hi Mike,
Okay, I think I know what the immediate problem is. Again, your
nested query goes like this:
select
VALUE, OFFSET
from dbo.CURVE
where CURVE_NAME = #curveName#
and CURVE
Hi Mike,
Okay, I think I know what the immediate problem is. Again, your
nested query goes like this:
select
VALUE, OFFSET
from dbo.CURVE
where CURVE_NAME = #curveName#
and CURVE_CATEGORY = #curveCategory#
So, if you pass in null as your paramete
Forgot to add that suggestions for better approaches would be greatly
appreciated (trying to do it with resultMap attribute at the moment).
- Mike
On 21/03/07, Mikael Andersson <[EMAIL PROTECTED]> wrote:
Hi Ted,
just started using iBATIS and the manual contains a similar approach, that
is why
Hi Ted,
just started using iBATIS and the manual contains a similar approach, that
is why I did it that way. I figured I would get that working and then tackle
the problem of N+1 select statements.
The table contains lots and lots of curves, where each curve has many curve
points. Stupid design I
Hi Mike,
How are you calling the mapped statement on the Java side?
Also, it's not clear why you're going to the trouble of a nested
select ("getCurvePoints") when it seems from your table design that
there will be one and only one x-y pair for a primary key. Would you
elaborate on why you are
Hi,
I'm new to iBATIS and need some help with a problem I'm having.
I have a table called CURVE which contains curve points for loads of curves
(graph curves), where each curve can have a dynamic number of curve points.
Table structure:
CURVE_NAME | CURVE_CATEGORY | OFFSET | VALUE
CURVE_NAME an
