Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-ALPHA3
    • Fix Version/s: 2.0-ALPHA4
    • Component/s: ORM
    • Security Level: All
    • Labels:
      None

      Description

      http://trac.doctrine-project.org/changeset/6982/

      The new processDeferredExpressionsStack does not look good. It processes all expressions. Previously, each (sub)query had its own stack.

      Now, when you do sth like this: "select u, (select max(o.id) from Other o) maxId from User u" you will trigger all validations at the end of the subquery. 'u' will be validated but is still undefined.

      Please explain why the old behavior with one stack for each (sub)query was not preserved.

      Also, things like

      $method = '_validate' . $item['method']; 
      

      lead to very fragile (bad) code.

        Activity

        Hide
        Guilherme Blanco added a comment -

        Just a little mis-comprehension of the new way I've build expressions validations.
        Resolving ticket.

        Show
        Guilherme Blanco added a comment - Just a little mis-comprehension of the new way I've build expressions validations. Resolving ticket.

          People

          • Assignee:
            Guilherme Blanco
            Reporter:
            Roman S. Borschel
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: