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] Updated: (JCR-1362) DatabaseJournal improperly finds tables in external schemas when used on Oracle
Date Mon, 11 Aug 2008 08:27:47 GMT

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

Martijn Hendriks updated JCR-1362:

    Attachment: JCR-1362.patch

The Oracle tablespace and SqlServer filegroup support have already been added (see JCR-968
and JCR-1295). The attached patch solves this issue.

I agree with Chris that we should very probably think about refactoring all or most of the
DB interaction into a set of utility classes. The fact that this Oracle issue has popped up
three times for different parts of the code (this issue, JCR-814 and JCR-582) underlines the
lurking maintenance problems.

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

View raw message