jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sascha Theves (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-1180) DatabaseFileSystem and DatabasePersistenceManager don't allow choice of db schema
Date Tue, 10 Jul 2012 16:28:34 GMT

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

Sascha Theves commented on JCR-1180:
------------------------------------

Can someone please increase the priority of this issue because it makes Jackrabbit unusable
in scenarios where you have to use a db schema name. And can somebody tell me in which version
this fix will be included?
                
> DatabaseFileSystem and DatabasePersistenceManager don't allow choice of db schema
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1180
>                 URL: https://issues.apache.org/jira/browse/JCR-1180
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>         Environment: All
>            Reporter: Kev Jackson
>            Assignee: Thomas Mueller
>            Priority: Minor
>         Attachments: DatabaseFileSystem.java, DatabasePersistenceManager.java, JCR-1180_2.2.7.patch,
TablePrefix.patch, TablePrefix.patch, jackrabbit-core.patch, postgresql.ddl, postgresql.ddl
>
>
> I have a need to store my repository objects under a different db schema than the default
for the rdbms (I'm using postgresql, so in my case the default is 'public')
> The current implementation of the DatabasePersistenceManager and DatabaseFileSystem do
not support changing the schema.
> Problems:
> - schemaObjectPrefix allows the user to add a table prefix, but you cannot use this to
set a schema ie <schema>.table, as the . is stripped out and replaced with an escaped
version
> - schema param currently refers to a ddl resource, not what people would naturally think
is the param to set the schema for the repository
> Fix:
> - rename the current schema -> schemaDDL
> - add an optional schema param which allows the user to select which schema they want
to use
> - improve error messages so that when an incorrect schemaDDL is chosen the user doesn't
have to dig through nabble etc to find an answer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message