You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@metamodel.apache.org by "Henry Saputra (JIRA)" <ji...@apache.org> on 2014/03/15 05:14:43 UTC

[jira] [Updated] (METAMODEL-14) Schema and table filter

     [ https://issues.apache.org/jira/browse/METAMODEL-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Saputra updated METAMODEL-14:
-----------------------------------

    Assignee:     (was: Henry Saputra)

> Schema and table filter
> -----------------------
>
>                 Key: METAMODEL-14
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-14
>             Project: Metamodel
>          Issue Type: New Feature
>            Reporter: Kasper Sørensen
>
> We sometimes encounter very big databases (mostly JDBC based) and even some DBAs who get annoyed that we use the JDBC metadata API to query for the schema structure. So...
> Make a common abstraction for filtering out certain schemas or tables. For instance a schema filter could provide either a pattern or a fixed set of schemas to include in the data context.
> It should be up to the datacontext to determine how to filter them. And at the least we should provide an interceptor implementation that will work for every datacontext implementation. Especially for JDBC it is important that the datacontext is aware of the filter, so it can apply it in the metadata calls to the DB.



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