Heh, yeah... what you said! Actually that's not something I've either ever seen done or ever tried... so I get to learn something today! w00t!
Thanks for the response, Shawn... J PS - I know what you meant in another post about dialing back your compositions... it can be a PITA. On Oct 17, 2008, at 2:46 PM, Shawn wrote: > > Just an FYI: > > "The other thing you can't do is define a column as part of a > relationship AND include as a property on the same object. Both of > these will result in a "duplicate column" error when it sends the > SQL > to the server for execution." > > You can, actually. Let's illustrate the problem, though... > > Let's say you have a column, called 'whatever'. You define > composition on that relationship, and not a property. That's fine, > except when you try to do a TQL query, you can't use that property as > a criteria. If I'm looking for whatever = :whatever, I'm going to get > an error in the tql query when it tells me "whatever" does not > exist. ... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
