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

Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2005/12/05 19:44:08 UTC

[jira] Updated: (DERBY-703) VTI Interface "IQualifyable" Semantics Unclear or Broken

     [ http://issues.apache.org/jira/browse/DERBY-703?page=all ]

Mike Matrigali updated DERBY-703:
---------------------------------

    Component: SQL
                   (was: Store)

> VTI Interface "IQualifyable" Semantics Unclear or Broken
> --------------------------------------------------------
>
>          Key: DERBY-703
>          URL: http://issues.apache.org/jira/browse/DERBY-703
>      Project: Derby
>         Type: Improvement
>   Components: SQL
>     Versions: 10.1.2.1, 10.1.2.0, 10.1.1.2, 10.1.1.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
>  Environment: This is not a platform-specific issue--more of the programming interface for internal VTI genration
>     Reporter: Kurt Westerfeld

>
> Our application wishes to generate some custom VTI implementations.  The VTI package has an interface called IQualifyable, which when implemented seems like it should pass all query parameters for the table.  It actually does this, but when implemented by the VTI, effectlively removes all "WHERE" clause filtering from the SQL engine processing the VTI table request.  Implementing this interface requires the VTI to handle all such processing.
> As an example, if you had a VTI with table columns "one", "two" and "three", and wanted to do some special processing for one of the columns by intercepting the IQualifyable interface (say, column "one"), processing for all three columns would be the responsibility for the VTI.
> I would propose one of two improvements to resolve this issue:
>    1. Allow the IQualifyable interface to simply have a "crack at it" to see what the query parameters are, and then allow additional selection processing to occur by the SQL engine, or 
>    2. Implement a new marker interface or sub-interface of IQualifyable which allows for the new semantic of intercepting the query parameters provided--similar to IQualifyable but allowing filtering to occur

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira