Can the lazy loading not be used for this?  I haven't looked into lazy
loading at all yet but it sounds like it would be a solution if it can
be used in this way...




-----Original Message-----
From: Gustavo Pistoia [mailto:[EMAIL PROTECTED]] 
Sent: 17 April 2002 19:53
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] Castor jdo limitation


Hi.
  I have a table with all the tasks performed by every user in my
company.
It�s huge, so even sql cannot respond quickly
to any query on this table. In my case, I have implemented one mapping
file, but classes doesn�t reflect all the relations between
objects. Cause I have a Model class, I can look at the reffered object
only
when I use it, not all the time. Obviously is not
as easy as the other mapping, but helps in your case. May be you can do
the
same.

     <class name="mypackage.Resource identity="legajo" access="shared">
          <map-to table="rqresources"/>
          <description>"Recursos"</description>
          <field name="legajo" type="string">
               <sql name="codigo_recurso" type="varchar"/>
          </field>
          <!--field name="boss" type="mypackage.Resource">
               <sql name="my_boss"/>               REPLACED
          </field-->
          <field name="bossCode" type="xsd:string">
               <sql name="my_boss"/>               <!--Call
ResourceModel.getTheBoss(bossCode)-->
          </field>

  The other thing is that you can made direct sql calls like this:
     CALL SQL select * from rqrecursos where.... AS mypackage.Resource.
  I guess is faster because go directly to the sql engine and sql
grammar
is bigger. I did something similar, and put this select under a method
in
my model class.

  I'm new with Castor, don�t trust me, better test it.





 

                    chamagne

                    <[EMAIL PROTECTED]        Para:
[EMAIL PROTECTED]                                             
                    trasbg.fr>                 cc:

                    Enviado por:               Asunto:      [castor-dev]
Castor jdo limitation                           
                    [EMAIL PROTECTED]

                    rasbg.fr

 

 

                    17/04/2002 13:00

                    Por favor, responda

                    a castor-dev

 

 




I found a big problem with castor jdo :
When you have classes which are interconnected, each time you request an
object, you get all the others objects that are connected to the
requested object...
So with such a method you could get all your database with a simple
query, considering the fact that all your objects are connected
together... It's a big problem, considering the fact that you might have
more than 100000 records per tables in your database....
Does anyone have such a problem???
If someone have an issue, please answer me...

Charly
Strasbourg Astronomical Observatory

-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
           unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to