[CAUSEWAY-1064] Allow DB schemas (or any other setup) to be performed as DN metamodel is built up for each class.

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: core-1.8.0
• Fix Version/s: 1.9.0
• Component/s: Persistence JDO
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 03/Mar/15 08:16
• Updated: 01/Sep/15 19:49
• Resolved: 12/Mar/15 15:09

Description

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.