jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JCR-1362) DatabaseJournal improperly finds tables in external schemas when used on Oracle
Date Mon, 11 Aug 2008 08:11:45 GMT

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

Martijn Hendriks reassigned JCR-1362:
-------------------------------------

    Assignee: Martijn Hendriks

> 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
>
> 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.


Mime
View raw message