You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Martijn Hendriks (JIRA)" <ji...@apache.org> on 2007/03/29 10:53:25 UTC

[jira] Commented: (JCR-814) Oracle bundle PM fails checking schema if 2 users use the same database

    [ https://issues.apache.org/jira/browse/JCR-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485112 ] 

Martijn Hendriks commented on JCR-814:
--------------------------------------

This breaks the MS-SQL bundle persistence manager, since it does not detect an existing schema. The fix is to override the checkSchema in the OracleBundlePersistenceManager, with the fix of Tobias for the metaData.getTables call. I guess that the issue should be reopenend, but I am not allowed to do that.

Regards,

Martijn Hendriks



> Oracle bundle PM fails checking schema if 2 users use the same database
> -----------------------------------------------------------------------
>
>                 Key: JCR-814
>                 URL: https://issues.apache.org/jira/browse/JCR-814
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.3
>            Reporter: Tobias Bocanegra
>         Assigned To: Tobias Bocanegra
>            Priority: Minor
>             Fix For: 1.3
>
>
> When using the OracleBundlePersistenceManager there is an issue when two users use the same database for persistence. In  that case, the checkSchema() method of the BundleDbPersistenceManager  does not work like it should. More precisely, the call "metaData.getTables(null,  null, tableName, null);" will also includes table names of other  schemas/users. Effectively, only the first user of a database is able to create  the schema.
> probably same issue as here: JCR-582

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