You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2014/07/25 09:43:38 UTC

[jira] [Created] (METAMODEL-72) Make SchemaBuilder capable of advising query strategy of multi-table DataContexts

Kasper Sørensen created METAMODEL-72:
----------------------------------------

             Summary: Make SchemaBuilder capable of advising query strategy of multi-table DataContexts
                 Key: METAMODEL-72
                 URL: https://issues.apache.org/jira/browse/METAMODEL-72
             Project: Metamodel
          Issue Type: Improvement
            Reporter: Kasper Sørensen


We now use SchemaBuilders for the JSON module and internally in the CouchDB module (METAMODEL-65). These work great when the DataContext itself is either a single-table backend or if it is aware of some of the traits of the schema builder.

To make SchemaBuilders truly pluggable, we need something more though. We cannot currently just plug in a SchemaBuilder, because the schema that is being built will influence the way backend-facing queries should be built too. If the schema that was built does not match with the table/collection names etc. of the backend store, then some translation logic is needed, and should be provided by the SchemaBuilder so that the DataContext can also plug in that query translation advice.



--
This message was sent by Atlassian JIRA
(v6.2#6252)