Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <14609904.1175169929244.JavaMail.jira@brutus>
Date: Thu, 29 Mar 2007 05:05:29 -0700 (PDT)
From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-814) Oracle bundle PM fails checking schema
 if 2 users use the same database
In-Reply-To: <33095659.1174655852335.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tobias Bocanegra resolved JCR-814.
----------------------------------

    Resolution: Fixed

Separated the table-existence-check from the schema creation and only override it in oracle persistence manager.

Committed revision 523680.


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