Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-13142

Separate storage of Projects and Applications from Components

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.2
    • Component/s: Compute Engine, Database
    • Labels:
      None
    • Edition:
      Community
    • Production Notes:
      None

      Description

      Note: this ticket was implemented as SONAR-12689, but that ticket was deleted by mistake.

       

      So far we store all components in a single table named `PROJECTS`. It includes projects, branches, files, portfolios and applications.

      Branches are also stored in another table, `PROJECT_BRANCHES`, which contains specific information related to branches.

      We want to keep reduce the scope of the table `PROJECTS`, and extract specific information regarding specific types of components out of `PROJECTS` into other tables.

      With this ticket, we rename the table `PROJECTS` to `COMPONENTS` and store some of the specific data about projects and applications in a new table named `PROJECTS`.

      Projects and applications will still be in the old table because some data like measures and issues can be related to any type of components including projects and applications.

      Until we are able to remove some of the columns from the old table, several operations will have to update both the old and new table to keep data in sync.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              duarte.meneses Duarte Meneses
              Reporter:
              duarte.meneses Duarte Meneses
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: