You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dietmar Gräbner (JIRA)" <ji...@apache.org> on 2006/10/03 13:19:20 UTC
[jira] Updated: (JCR-582) No support for Oracle schemas
[ http://issues.apache.org/jira/browse/JCR-582?page=all ]
Dietmar Gräbner updated JCR-582:
--------------------------------
Attachment: patch-582.rar
New versions of OracleFileSystem and OraclePersistenceManager.
The only modification is in the checkSchema method.
> No support for Oracle schemas
> -----------------------------
>
> Key: JCR-582
> URL: http://issues.apache.org/jira/browse/JCR-582
> Project: Jackrabbit
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.1
> Environment: Oracle database: the problem occurs when using Jackrabbit in more than one schema on the same oracle instance.
> Reporter: Dietmar Gräbner
> Priority: Minor
> Attachments: patch-582.rar
>
>
> Jackrabbit assumes that the table name (f.e.: prefix + fs_entry) is unique across all schemas used on one oracle instance. So two Jackrabbit instances using two schemas on the same Oracle instance won't work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira