OK so the bug is definitely a bug... I've gotten details to Mark.
However, I am a goober. I was sitting there looking at the Transfer
docs, trying to work out my workaround for the problem. Initially I
used the ignore-update and ignore-insert attributes to have both the
ID and the relationship properties on the necessary objects and then
used them in the join statements. What I never spotted in the doco
was that I could do this:
SELECT
c.ID AS CompanyID,
a.ID AS AuctionID,
i.ID AS InvoiceID,
p.ID AS PaymentID,
pm.ID as PaymentMethodID,
*
FROM company AS c
JOIN auction AS a
JOIN invoice AS i
JOIN payment AS p
JOIN paymentMethod pm ON p.paymentMethod
WHERE
c.ID = :companyID
AND p.deleted != p.refunded
AND p.deleted = :deleted
So you can specify the object to be joined to and the
object.relatedProperty to specify a subset of possible joins that are
possible. Duh. I had a suspicion that I could do this, but trying to
translate from regular SQL to TQL was proving difficult for my poor
pitiful brain that day.
Anyway, this works just fine. Thanks Mark for setting my brain on the
right path. :)
J
On Nov 26, 2008, at 3:00 PM, Mark Mandel wrote:
>
> Jared,
>
> Looks like a bug - but, can you lay out the the basic config for me,
> so I can see the object relationships, as I think there are a couple
> of m2m relationships in there.
>
> Mark
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
