[
https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969414#action_12969414
]
Marc Morin commented on OFBIZ-4041:
-----------------------------------
Good point Scott. We have "removed" the bulk operations in our implementation
for specifically that reason... We've noticed that even though these are bulk
operations, they don't appear to be from an API point of view. There isn't
much to help guide the developer that using these API's will circumvent all ECA
activity....
We had thought about only doing the bulk operation iff there are no ECAs
defined for the entity and operation defined. Otherwise, leave it as bulk.
But that too would appear to be dangerous since there are unknown side affects
of not running the ECA.
Not sure what the best/good compromise is for the bulk vs normal operation is.
Just seems incorrect to bypass the ECA. Not that "disabling" the eca via the
entityengine.xml also causes the materialized views to not always maintaining
it's results.
> Materialized views
> ------------------
>
> Key: OFBIZ-4041
> URL: https://issues.apache.org/jira/browse/OFBIZ-4041
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: Release Branch 10.04
> Reporter: Marc Morin
> Attachments: OFBIZ-4041.patch
>
>
> We make extensive use of view entities in our ofbiz application. We have
> noticed that when there is a large dataset and under some complex views, the
> query performance was not the best (not a index issue, just complex joins,
> etc...).
> With some commercial databases like Oracle, etc... we would have used
> materialized view semantics available for these dbms, but we are using
> PostgreSQL.
> So, we have extended the entity layer in Ofbiz to perform the
> materialization. This is pretty slick as all you need to do is the following:
> <view-entity name="myView" materialize="true">...</view-entity>
> and the system will do the following:
> - create a backing entity called "myView" that has the same fields as the view
> - backing entity has all the indexes inherited from the component entities
> - relations (fk,...) inherited from the component entities.
> - perform all the ECA actions automatically on all entities used in the view
> (direct members and nested members if case of view on views). (This is an
> eager update strategy only).
> So, the application doesn't change, it still accesses "myView", but now, it's
> result is returned from the backing entity instead of the complex SQL
> statement.
> We're pretty excited about this feature!!! Really pushes Ofbiz framework to
> next level and allows materialized views to be more broadly used on dbms that
> don't naturally support it.
> We are prepared to contribute this feature back to the community if desired.
> A note of caution about it though.... we have added a visitor pattern to the
> model entities and this feature makes use of it. It would need to come with
> it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
