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/05/03 21:56:14 UTC

[jira] [Commented] (METAMODEL-52) Expose MetaModel DataContexts through a JDBC compliant Driver

    [ https://issues.apache.org/jira/browse/METAMODEL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988802#comment-13988802 ] 

Kasper Sørensen commented on METAMODEL-52:
------------------------------------------

I posted a patch for this here: https://reviews.apache.org/r/21054/

It now supports querying (only via Statement.executeQuery()), but not anything more advanced than that ... Should give an idea of the feature though. Functionality can absolutely be made more advanced to include compiled queries, updates etc.

> Expose MetaModel DataContexts through a JDBC compliant Driver
> -------------------------------------------------------------
>
>                 Key: METAMODEL-52
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-52
>             Project: Metamodel
>          Issue Type: New Feature
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>            Priority: Minor
>
> Maybe a wild idea, but one that tickles my curiousity: Would it make sense to build a JDBC driver that allows exposing DataContexts as if they are normal relational databases. Since we now have a SQL parser in place and also have a solid metadata API, we should be able to quite easily adapt to the JDBC API.
> Although I don't particularly like the JDBC API, it would make MetaModel very accessible for everyone who already knows JDBC. That way we can immediately offer connectivity to all of our datastores through a wellknown API. (And hopefully over time those users will start being more interested in the native MetaModel API).



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