I don't believe so. You'll need to remove it and either use TQL to do your
list query, or write your own list query yourself outside of Transfer. Part
of the point of Transfer is that you're dealing with Objects and their
relationships, not tables and foreign keys. So trying to "go behind it's
back" and do things like using foreign key columns directly is discouraged.

On Fri, Mar 6, 2009 at 10:39 AM, Dustin Martin <[email protected]> wrote:

>
> I have a one to many relationship between my parent class called Claim
> and a child class called Item. My item table contains both an Item_ID
> and Claim_ID column. The Claim_ID column is the foreign key. In the
> Item definition XML I have specified the following:
>
> ITEM
>
> <id name="itemID" type="numeric" column="Item_ID" />
> <property name="claimID" type="numeric" column="Claim_ID"  />
>
> CLAIM
>
> <onetomany name="Item" lazy="true">
>        <link to="claim.Item" column="Log_ID" />
>        <collection type="array">
>                <order property="upc" />
>        </collection>
> </onetomany>
>
> Since I have the claimID property specified in the item definition in
> addition to the one to many relationship specified in Claim, Transfer
> puts the Claim_ID column into my queries twice which throws an error
> when I try to save an item. However, I need to be able to run list
> queries based on the Claim_ID column in Item so I cannot take out the
> claimID property from the XML. Is there a way to keep both in there?
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer

You received this message because you are subscribed to the Google Groups 
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to