Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-1362

DatabaseJournal improperly finds tables in external schemas when used on Oracle

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.3.3, 1.4
    • core 1.4.6
    • jackrabbit-core, sql
    • None

    Description

      The DatabaseJournal currently calls database metadata to determine if the journal table has already been created. It uses the following code to do so:

      ResultSet rs = metaData.getTables(null, null, tableName, null);

      The Oracle driver sometimes will return the table if it is in another schema on the same database. Other DBMS code within JackRabbit has a specific Oracle version that handles this case. In order for the journal table to be properly created, Oracle databases will need the schema name included in the getTables() call.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            cschmidt Chris Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment