Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Labels:
      None

      Description

      Up and down operations should only put commands on a stack that is then executed after up() or down() have been processed.

      Currently there are two implicit stacks:

      1. addSql()
      2. The changes done to the $schema instance.

      With DMIG-26 $schema is an explicit change that adds to a stack.

      This should be unified to be one single stack called "operations" and they should be linearly processed.

        Activity

        Benjamin Eberlei created issue -
        Benjamin Eberlei made changes -
        Field Original Value New Value
        Description Up and down operations should only put commands on a stack that is then executed after up() or down() have been processed.

        Currently there are two implicit stacks:

        1. addSql()
        2. The changes done to the $schema instance.

        With DMIG-28 $schema is an explicit change that adds to a stack.

        This should be unified to be one single stack called "operations" and they should be linearly processed.
        Up and down operations should only put commands on a stack that is then executed after up() or down() have been processed.

        Currently there are two implicit stacks:

        1. addSql()
        2. The changes done to the $schema instance.

        With DMIG-26 $schema is an explicit change that adds to a stack.

        This should be unified to be one single stack called "operations" and they should be linearly processed.

        This list may be incomplete, as errors occurred whilst retrieving source from linked applications:

        • Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DMIG-27, expand=changesets[0:20].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Benjamin Eberlei
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: