[
https://issues.apache.org/jira/browse/JCR-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1180:
-------------------------------
Fix Version/s: (was: 1.4)
Dropping this from 1.4. The proposed patch seems too complex to me and
introduces a backwards-incompatible configuration change. I'd rather see
something that works within the scope of the existing schemaObjectPrefix option.
> DatabaseFileSystem and DatabasePersistenceManager don't allow choice of db
> schema
> ---------------------------------------------------------------------------------
>
> Key: JCR-1180
> URL: https://issues.apache.org/jira/browse/JCR-1180
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Environment: All
> Reporter: Kev Jackson
> Priority: Minor
> Attachments: jackrabbit-core.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
