Actually Calvin seems to have responded to the wrong thread. His problem
actually is a mySQL problem and the subject is Exception when connecting to
DB. This thread is aptly named, because the original message for this
thread is a MSSQL problem.
Brad
On 2/23/07, Yee, Richard K CTR DMDC
iBatis came back with an error message indicating too many objects were
being returned for executeQueryForObject.
Brad
On 2/20/07, Brad Handy [EMAIL PROTECTED] wrote:
Wouldn't I have to give unique column names for those identifying the
child data?
For example
table parentChild
It seems to me this configuration is the problem:
procedure id=elions.bas.procCounter parameterClass=hashMap
{
call EKA.SISTEM_KONTROL_SPAJ.GENERATE_COUNTER (
#hasil:varchar#,#msco_number:number#, #lca_id:varchar#,
#prefix:varchar#,
#suffix:varchar#,
... resultMap=Node/
...
I don't see any reason why that would cause any problems...perhaps try it
and let us know.
Cheers,
Clinton
On 2/19/07, Clinton Begin [EMAIL PROTECTED] wrote:
Oh...is it a self join?
Clinton
On 2/19/07, Brad Handy [EMAIL PROTECTED] wrote:
I guess I'll have to take
/
...
I don't see any reason why that would cause any problems...perhaps try it
and let us know.
Cheers,
Clinton
On 2/19/07, Clinton Begin [EMAIL PROTECTED] wrote:
Oh...is it a self join?
Clinton
On 2/19/07, Brad Handy [EMAIL PROTECTED] wrote:
I guess I'll have to take a different approach
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
Parent 1
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 table. I would like to avoid the N+1 selects with this construct, but
it's unclear from the documentation
