[
https://issues.apache.org/jira/browse/OFBIZ-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526696
]
Oscar Pablo commented on OFBIZ-1232:
------------------------------------
By using the tag <filter> to enter filter conditions, we are not binding the
filtering to the join. That is, we can apply a filter even on a single table
view. Using the filter tag inside or bound to the <view-link> tag makes the
user define a view link to be able to define a filter.
Control over "filter conditions" to avoid redundant filters I think is not a
critical thing, cause developer/designer can easily control that. And, by the
way, if not controlled, it doesn't cause an error.
> Data filtering in entity views
> ------------------------------
>
> Key: OFBIZ-1232
> URL: https://issues.apache.org/jira/browse/OFBIZ-1232
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Oscar Pablo
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: filter_views.diff
>
>
> OfBiz allows the creation of views based on the database model. But the data
> selection is done only by join. It would be great to select the data also by
> value. And, in some cases, it avoids workarounds and a cleaner code.
> The proposal is to create a new tag inside view-entity tag from
> entitymodel.xml with the following syntax:
> <filter entity-alias="<table_alias>" field-name="<field_name>"
> operator="<operator:equals, not-equals, like...>" value="<value_to_select>"/>
> these tag could appear from 0 to N times. When N times, all filter criteria
> must match with the data to select it.
> I am attaching the xsd and the code I made...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
