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 2015/12/07 14:56:11 UTC
[jira] [Created] (METAMODEL-217) Add fallback strategy in JDBC
module for queries that are not rewriteable
Kasper Sørensen created METAMODEL-217:
-----------------------------------------
Summary: Add fallback strategy in JDBC module for queries that are not rewriteable
Key: METAMODEL-217
URL: https://issues.apache.org/jira/browse/METAMODEL-217
Project: Apache MetaModel
Issue Type: Improvement
Affects Versions: 4.4.1
Reporter: Kasper Sørensen
In our JDBC module we currently rewrite all MetaModel queries into SQL queries that we submit to the database. This works well and is very effecient ... when it works.
But there are a few scenarios (and potentially more coming) which don't work. For instance, we currently don't support rewriting scalar functions of non-select clauses (this could be improved though) and we don't support custom aggregation functions either.
So an improvement would be to check the query for these special cases and when we encounter them, execute the query using MetaModel's query postprocessing engine instead. This will for sure be more expensive to do, but would retain compatibility and uniformness across the connectors of MetaModel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)