Using the new option mechanism, the association storage strategy should be configurable for the MongoDB dialect on a per entity/property base, via annotations and API.
* Move the annotation, enum and programmatic APIs from _couchdb_ to _core_ (/)
* Have only {{IN_ENTITY}} and {{AS_DOCUMENT}} on the enum in _core (/)
* Provide {{@StoreAssociationsInSeparateCollection}} in MongoDB
* Implement association handling in {{MongoDBDialect}} based on the setting applying for a given association similar to {{CouchDBDialect}}
ML reference: http://lists.jboss.org/pipermail/hibernate-dev/2013-December/010741.html
|
