db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Vatkov" <bvat...@globaltech-bg.com>
Subject isForReferenceOnly() ? why
Date Fri, 26 Mar 2004 09:08:44 GMT
Hello Guys,

I were trying to split my large database schema into separate *-schema.xml files
and the result is that if i have multiple schemas and of course relations cross the schemas
I have miss-generated a few valuable methods inside generated OM classes
example: (init and add relations)

     * Temporary storage of $collName to save a possible db hit in
     * the event objects are add to the collection, but the
     * complete collection is never requested.
    protected void init${relCol}()

     * Method called to associate a $tblFK.JavaName object to this object
     * through the $className foreign key attribute
     * @param l $className
     * @throws TorqueException
    public void add${relColMs}($className l) throws TorqueException

as long as they are controlled by the isForReferenceOnly()
this way i lose a lot of the power of torque om classes.

So why is this restriction of code generated based on the fact wheter the table is or is not
a part of the same schema ?
Could be this fixed somehow ? I tought I can remove conditions concerning the isForReference()
issue..but i am not sure ..
Am I worng/right ? Any clues?

With best regards,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message