Re: Why is appendObjectMatch (objectMatchTranslator) called late in query translation?

From: Mike Kienenberger (mkienen..mail.com)
Date: Tue Aug 22 2006 - 17:54:05 EDT

  • Next message: Mike Kienenberger: "Outer join status [Was: Building null-checking expression without calling objectNode() twice?]"

    I guess this is because it can generate multiple clauses.

    On 8/22/06, Mike Kienenberger <mkienen..mail.com> wrote:
    > I'm trying to track down why appendObjectMatch (objectMatchTranslator)
    > generates sql late in the process for a clause rather than immediately
    > during objectNode processing.
    >
    > So far, I don't understand.
    >
    > detectObjectMatch is called early in startNode to create/reset the
    > objectMatchTranslator.
    >
    > appendLiteral and processRelTermination configure
    > objectMatchTranslator during objectNode by adding DataObjects or
    > Relationships or ObjectIds to the objectMatchTranslator.
    >
    > finishedChild (operator handler) stores sql and expression in
    > objectMatchTranslator if matchingObject rather than to the global
    > buffer.
    >
    > appendObjectMatch() is called after all of the objectNode and
    > finishChild method calls during endNode.
    >

    This archive was generated by hypermail 2.0.0 : Tue Aug 22 2006 - 17:54:28 EDT