(preview) OGM-140 OGM-141 table exposed to DatastoreProvider and embeddable collection info provided to AssociationKey #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been working on two things lately
Expose table and column information to the
DatastoreProvider
This is useful to build the right buckets in some NoSQL engines. In particular Cassandra can now use
specific tables instead of the generic one we are using currently.
Let me know how it works.
Expose infos on collection of embedded to
AssociationKey
One thing I want out of the MongoDB Dialect is the ability to store collections of embeddable within the entity document itself instead of in a different document. I have added a couple of information to
AssociationKey
in that effect:To the MongoDB writers, let me know if the information is useful and if you can store collections of embeddable within the entity document itself.