[
https://issues.apache.org/jira/browse/ISIS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1064.
-------------------------------
Resolution: Fixed
> Allow DB schemas (or any other setup) to be performed as DN metamodel is
> built up for each class.
> -------------------------------------------------------------------------------------------------
>
> Key: ISIS-1064
> URL: https://issues.apache.org/jira/browse/ISIS-1064
> Project: Isis
> Issue Type: New Feature
> Components: Core: Objectstore: JDO
> Affects Versions: core-1.8.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.9.0
>
>
> To support modularization (eg of isisaddons), it'd be good practice to allow
> classes to be mapped to specific (DB) schemas, rather than the default
> "public" (HSQLDB/Postgres) or "dbo" (MSSQL) schema.
> This requires some mechanism to intercept the creation process and create the
> schema before hand.
> This enhancement is:
> - provide the ability to register a listener class (implementing
> org.datanucleus.metadata.MetaDataListener), so that this can be done on
> start-up
> - provide a default implementation that works "out-of-the-box" for (at least)
> HSQLDB, PostgreSQL and MS SQL Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
