Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1610446984.1215650491716.JavaMail.jira@brutus>
Date: Wed, 9 Jul 2008 17:41:31 -0700 (PDT)
From: "Pinaki Poddar (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-655) Class level query filter
In-Reply-To: <1580930033.1215650491668.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pinaki Poddar updated OPENJPA-655:
----------------------------------

    Attachment: class-filter.patch.txt

A prototype for adding a class-level filter that augments any query

> Class level query filter 
> -------------------------
>
>                 Key: OPENJPA-655
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-655
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: query
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>         Attachments: class-filter.patch.txt
>
>
> A class-level query filter that applies to all queries implicitly is a useful functionality and available in similar software product [1].
> The base functionality is:
> a) A class can be annotated with a query
> @Entity
> @Filter(query="SELECT x FROM PObject x WHERE x.field = f1 AND x.status =! DONE")
> public class PObject {...}
> b) Any query on class PObject will augment the class-level filter predicates. 
> c) @Filter query can be parametrized. The parameters can be set on current FetchPlan.
> Will attach a draft/prototype for such functionality. Please take a look and let me know your valued comments.
> [1] http://www.hibernate.org/hib_docs/reference/en/html/filters.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.