Hi
Low,
Why
don’t you post it to the list. I don’t
remember
you
proposed a patch like that before.
Even
if I don’t have time to review it right the
way,
user
would need it may benefit from it, if they
need
it
right now.
Thomas
-----Original
Message-----
>From: Low Heng Sin
[mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 22, 2002 6:25
PM
>To:
[EMAIL PROTECTED]
>Subject: Re: [castor-dev] JDO
Performance Issue ... Again
>
>I've implemented the lazy/non-lazy
loading of 1:n relation in
>separate query solution and would like to share it with
anyone
>who is interested with it. Thomas, would u mind to share
your
>plan solution with me so that I can digest how different
is my
>solution and probably adjust it closer to what u have in
mind.
>
>thanks.
>
>Regards,
>Low
>-----Original
Message-----
>>From: Thomas Yip
[mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, April 23, 2002
2:33
>>To:
[EMAIL PROTECTED]
>>Subject: Re: [castor-dev] JDO
Performance Issue ... Again
>>Hi Jan,
>>
>>
>>You’re right. It is a fundamental
limitation.
>>It can’t be fixed without a lot of
work. It has
>>been discussed in the mailing list a
few times
>>in the past.
>>
>>We had plan for it. However, it becomes
obvious
>>that we are not going to have enough
resource
>>on execute it any time
soon.
>>
>>
>>
>>
>>Thomas
>>
>>-----Original
Message-----
>>>From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
>>>Sent: Monday, April 22, 2002 7:25
AM
>>>To:
[EMAIL PROTECTED]
>>>Subject: Re: [castor-dev] JDO
Performance Issue ... Again
>>>
>>>Christoph wrote:
>>>>Perhaps you could gain a little
speed by using OQLQueries instead of
>>>>iterating over the resulting
lazy collections if you need only
>>>>specific
objects.
>>>Tried that still too slow. This is
IMO a fundemental flaw I wish to see
>>>addressed ASAP. I tried solving
this myself without luck. That is why
>>>i ask core contributors to castor
where this is on their list of priorities.
>>>I raised this issue several months
ago and i can not understand why
>>>this hasnt gotten more attention.
My project is dying on this flaw and
>>>if there is no fix within
forseeable future I will have to drop castor
>>>completely.
>>>>Otherwise refactoring this
collection handling part would be definitly
>>>>an improvement
...
>>>It's not only an improvement it is
a requirement!! If this doesn't get fixed
>>>castor JDO is completely useless
for any projects with anything but the
>>>simplest class
hierachies.
>>>Regards
>>>Jan H. Hansen
>>>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe
castor-dev
>>>
>>
>
