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

Stop support of the property "sonar.jdbc.schema"

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2
    • Component/s: Database
    • Labels:
      None

      Description

      This property was sometimes useful for Oracle or PostgreSql users :

      • PostgreSql : using this property was mandatory to use a schema different that the default "public" one. The same use case can be covered by setting the required "search_path" property value for the PostgreSql SonarUser
        ALTER USER sonarUser SET search_path to mySoanrQubeSchema
        
      • Oracle : using this property was mandatory when the there was a table naming conflict between the Oracle SonarQube schema and some other Oracle schemas. For instance, when having two different SonarQube schemas in the same Oracle DB. In such case, privileges associated to the SonarQube Oracle users should be decreased or a trigger should be defined on Oracle side to automatically alter the SonarQube Oracle user session when establishing a new connection
        ALTER SESSION SET current_schema=MY_SONARQUBE_SCHEMA"
        

      The only real drawback of this suppression is that a DB SonarQube user can't be used anymore to access to two different SonarQube schemas located on the same DB.

        Attachments

          Activity

            People

            Assignee:
            simon.brandhof Simon Brandhof (Inactive)
            Reporter:
            freddy.mallet Freddy Mallet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved: