[jira] Updated: (JCR-1362) DatabaseJournal improperly finds tables in external schemas when used on Oracle

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1362:
-------------------------------

    Fix Version/s: core 1.4.6

Merged to the 1.4 branch in revision 695887.

> DatabaseJournal improperly finds tables in external schemas when used on Oracle
> -------------------------------------------------------------------------------
>
>                 Key: JCR-1362
>                 URL: https://issues.apache.org/jira/browse/JCR-1362
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, sql
>    Affects Versions: 1.3.3, 1.4
>            Reporter: Chris Schmidt
>            Assignee: Martijn Hendriks
>             Fix For: core 1.4.6
>
>         Attachments: JCR-1362.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.